scheduled updates that do not require signoffs show they require a signoff from all teams
Categories
(Release Engineering Graveyard :: Applications: Balrog (frontend), enhancement, P3)
Tracking
(Not tracked)
People
(Reporter: jlund, Unassigned)
Details
Attachments
(2 files)
The bug description may be wrong but here is what I'm observing.
I scheduled a change for a widevine rule. I did this so I could queue a lot of changes and have others review it.
I believe once the scheduled time was met, it put the update in effect. I say "I believe" because in this case, it was a scheduled delete and the scheduled change still appears after deadline.
However, while waiting, the UI suggested I needed sign off from every team Balrog knows about. Even though it gave no UI option to sign off.
Screenshots to be attached
| Reporter | ||
Comment 1•7 years ago
|
||
| Reporter | ||
Comment 2•7 years ago
|
||
| Reporter | ||
Comment 3•7 years ago
|
||
hm, this might have just been because they were localtest channels. still, https://bug1526009.bmoattachments.org/attachment.cgi?id=9042244 probably shouldn't show it requires sign off from all those teams.
Comment 4•7 years ago
|
||
Certainly seems like the signoff requirements were incorrectly computed. I'll have a look into why some time.
Updated•6 years ago
|
Comment 5•6 years ago
|
||
Mass closure of old Balrog UI bugs. We've built a new UI in https://github.com/mozilla-frontend-infra/balrog-ui, and any issues which are still valid should be filed as Issues there.
Updated•6 years ago
|
Description
•