Closed
Bug 1310236
Opened 8 years ago
Closed 8 years ago
Balrog should refuse to make direct changes to objects that require Signoff
Categories
(Release Engineering Graveyard :: Applications: Balrog (backend), defect)
Release Engineering Graveyard
Applications: Balrog (backend)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 1310210
People
(Reporter: bhearsum, Assigned: bhearsum)
References
Details
When Required Signoffs are implemented, Balrog should absolutely not make direct changes to objects that require Signoff. This should be enforced at a low level (probably AUSTable).
One thing that we may want to consider is converting direct updates like this into a Scheduled Change rather than rejecting them outright. This may be more convenient for the user, and possibly simplify some of the other implementation. OTOH, this might just be confusing.
|
Assignee | |
Comment 1•8 years ago
|
||
This ended up making sense to do as part of bug 1310210.
Assignee: nobody → bhearsum
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → DUPLICATE
|
||
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
•