Closed
Bug 1343913
Opened 7 years ago
Closed 5 years ago
required signoffs should be shown immediately
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), enhancement, P3)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: bhearsum, Unassigned)
Details
(Whiteboard: [lang=python][ready])
Currently, when a new Scheduled Change that requires signoff is added, a page refresh is required to have the signoffs it requires be shown. For most use cases this isn't a big deal, because Scheduled Changes are shown on a different page than where a change is Scheduled, but it's a pretty big papercut. The best way to see this is to schedule a change for a new Rule. You'll see "Before it can be enacted, this change must be signed off on by:", but nothing below it. This happens beacuse the endpoint that lets you schedule things (https://github.com/mozilla/balrog/blob/master/auslib/admin/views/scheduled_changes.py#L67) does not return information about the required signoffs, whereas the endpoint that returns all existing scheduled changes (https://github.com/mozilla/balrog/blob/master/auslib/admin/views/scheduled_changes.py#L23) does. We should probably also return required signoffs when modifying a scheduled change) https://github.com/mozilla/balrog/blob/master/auslib/admin/views/scheduled_changes.py#L91, because doing so may change what is required.
Reporter | ||
Updated•7 years ago
|
Priority: P2 → P3
Reporter | ||
Updated•7 years ago
|
Mentor: bhearsum
Reporter | ||
Updated•7 years ago
|
Mentor: bhearsum
Reporter | ||
Comment 1•6 years ago
|
||
I need to unassign this for now because I don't have the time to take on any additional mentoring/reviewing at the moment. Sorry =\
Assignee: collins.abitekaniza → nobody
Comment 2•6 years ago
|
||
(In reply to Ben Hearsum (:bhearsum) from comment #1) > I need to unassign this for now because I don't have the time to take on any > additional mentoring/reviewing at the moment. Sorry =\ It's alright :)
Reporter | ||
Comment 3•5 years ago
|
||
We're currently working on a new version of the UI, and bugs like this are unlikely to be fixed in the current one.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WONTFIX
Updated•5 years ago
|
Product: Release Engineering → Release Engineering Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•