Closed
Bug 1241760
Opened 9 years ago
Closed 9 years ago
balrog UI rules page should separate rule items by product and channel
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), defect)
Release Engineering Graveyard
Applications: Balrog (frontend)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: jlund, Assigned: njirap, Mentored)
References
()
Details
(Whiteboard: [lang=js])
during the recent Balrog UI tutorial I was thinking about a new layout for the balrog rules UI to make it easier to see which rules are related.
as a specific example:
I was thinking that the rules themselves don't need much width space so we could introduce columns and side scrolling (think trello cards)
So we could split each 'row' of rules by product (e.g. 'Firefox') and then each column in the 'Firefox' row we separate by channel, e.g. 'nightly'.
additional thoughts:
- Since rules allow for channel globbin with a *, I suppose we would have the * based rules always at the first few columns.
- if more than one rule has the same product and channel, we then order them by priority.
Comment 1•9 years ago
|
||
Thanks for filing! I think this is a great idea - particularly when trying to look at a channel plus its localtest/cdntest variants.
Another thing to keep in mind here is that in addition to globs, a rule with a NULL product or channel is treated the same as if it were simply "*".
Updated•9 years ago
|
Mentor: bhearsum
Whiteboard: [lang=js]
Updated•9 years ago
|
Comment 2•9 years ago
|
||
This landed in production today. Thanks Njira!
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Comment 3•8 years ago
|
||
Commit pushed to master at https://github.com/mozilla/balrog
https://github.com/mozilla/balrog/commit/1cfa464a3a3448bd81b230c39f2b897923797534
[balrog-ui] bug 1241760: balrog UI rules page should separate rule items by product and channel. r=bhearsum
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
•