Auditable Publish logs.
Bug #1491163 reported by
Robert Bruce Park
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bileto |
Fix Released
|
Critical
|
Robert Bruce Park | ||
CI Train [cu2d] |
Fix Released
|
Critical
|
Robert Bruce Park |
Bug Description
Steve has requested auditable publish logs. This should be modeled similarly to the existing Comment class, such that publish records can be created but not edited or deleted. they should record who clicked publish, what was published, and what job options were used.
Changed in bileto: | |
importance: | Undecided → High |
Changed in bileto: | |
importance: | High → Critical |
Changed in cupstream2distro: | |
status: | New → Triaged |
importance: | Undecided → Critical |
assignee: | nobody → Robert Bruce Park (robru) |
Changed in bileto: | |
status: | Triaged → Fix Released |
Changed in cupstream2distro: | |
status: | Triaged → Fix Released |
To post a comment you must log in.
User stories:
* as a user of the train, when looking at a landing in bileto I want to be able to (easily) find out who published it so that I can ask them a question about its status at time of publication
* as an Ubuntu developer, I want to know who signed off on a particular problematic packaging change via the train
* as an Ubuntu archive admin, I want the train to enforce the policy that all packaging changes sent via the train are signed off by an Ubuntu developer with the relevant upload rights, and be able to verify this.