Closed
Bug 1363452
Opened 8 years ago
Closed 7 years ago
view for showing scheduled changes in context of the rest of the rules
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), enhancement, P1)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
(Whiteboard: [lang=js][lang=html])
Attachments
(1 file)
As we start using Scheduled Changes for everything it's going to be important that we're able to easily evaluate them in the context of the existing Rules. At the moment, this has to be done in one's head by looking at both the Rules page and the Scheduled Rule Changes page, and combining the two in your head. One way to make this easier is to have a view like the main Rules page, but include Scheduled Changes in it, with some indication of what's going added, updated, or removed. Eg: a Rule that is scheduled for deletion would not be removed from the list, but would be marked in some way.
Assignee | ||
Updated•8 years ago
|
Whiteboard: [lang=js][lang=html]
Assignee | ||
Comment 1•7 years ago
|
||
As part of bug 1301724 I'm loading scheduled changes as part of the main Rules page - which means we'll have access to all of that data there. Maybe we can put the scheduled values (if they differ) in the same cards as the primary Rules? Because we only allow one scheduled change per Rule at a time, we shouldn't have any conflicts...
Assignee | ||
Updated•7 years ago
|
Assignee: nobody → bhearsum
Priority: P3 → P1
Assignee | ||
Comment 2•7 years ago
|
||
Attachment #8905647 -
Flags: review?(jlorenzo)
Updated•7 years ago
|
Attachment #8905647 -
Flags: review?(jlorenzo) → review+
Comment 5•7 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/6ddb651bdf8962626c4bd309dfb9e0efc3a026eb
bug 1363452: view for showing scheduled changes in context of the rest of the rules (#394). r=nthomas,jlorenzo
Assignee | ||
Comment 6•7 years ago
|
||
This is now in production.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
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
•