Closed
Bug 1301724
Opened 9 years ago
Closed 8 years ago
add an indication on rules page of whether or not a rule or release has a changed scheduled
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), defect, P1)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bhearsum, Assigned: bhearsum, Mentored)
References
Details
(Whiteboard: [lang=js][ready][good first bug])
Attachments
(1 file)
Similar to bug 1113689, it would be really nice to have an indication in the Rules UI if a Rule has a change scheduled.
| Assignee | ||
Comment 1•9 years ago
|
||
I don't think this needs any backend support, but it will require an extra call to grab the current scheduled changes.
Priority: -- → P3
Whiteboard: [lang=js] → [lang=js][ready][good first bug]
| Assignee | ||
Updated•8 years ago
|
Mentor: bhearsum
| Assignee | ||
Updated•8 years ago
|
Summary: add an indication on rules page of whether or not a rule has a changed scheduled → add an indication on rules page of whether or not a rule or release has a changed scheduled
| Assignee | ||
Comment 2•8 years ago
|
||
| Assignee | ||
Comment 3•8 years ago
|
||
My current implementation is 100% frontend. I think it would be better to make the backend return this information, but I had trouble making it work in the short term. https://github.com/mozilla/balrog/compare/master...mozbhearsum:scheduled-change-indicator?expand=1 was my attempt.
| Assignee | ||
Updated•8 years ago
|
Priority: P3 → P1
Updated•8 years ago
|
Attachment #8899560 -
Flags: review?(jlorenzo) → review+
Comment 4•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/54759130b6f70736d4022f0917c1006f7dc902a2
bug 1301724: add an indication on rules page of whether or not a rule has a change scheduled (#375). r=jlorenzo
| Assignee | ||
Comment 5•8 years ago
|
||
This is now in production.
Status: ASSIGNED → RESOLVED
Closed: 8 years ago
Resolution: --- → FIXED
Updated•6 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
•