Setting a bug confidential after its creation creates a ghost bug
Bug #64017 reported by
Francis J. Lacoste
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Fix Released
|
Critical
|
Brad Bollenbach | ||
Bug Description
On staging:
1) Create a new bug on Launchpad product.
2) Change the visibility of the bug to 'Confidential'
You end up the only subscribers on the bug which means that you are the only one that can access it.
I would expect either:
a) That the security and/or bug contacts be added to the list of subscribers automatically
or
b) get a warning about the fact that I'm now the only one being able to see that bug. With a suggestion that I should subscribe other people that should have access to the bug.
Revision history for this message
| Francis J. Lacoste (flacoste) wrote | #1 |
| Changed in launchpad: | |
| status: | Unconfirmed → Confirmed |
| Changed in launchpad: | |
| assignee: | nobody → bradb |
| status: | Confirmed → In Progress |
| Changed in launchpad: | |
| importance: | Undecided → Critical |
Revision history for this message
| Brad Bollenbach (bradb) wrote | #2 |
| Changed in launchpad: | |
| status: | In Progress → Fix Committed |
| Changed in launchpad: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Bradb says that the reason behind this regression is that the view was switch to LaunchpadEditFo