Marking an existing bug as "security" does not subscribe security contact
Bug #365217 reported by
Kees Cook
This bug report is a duplicate of:
Bug #61909: When the security flag changes, also change the subscription of the security contact.
Edit
Remove
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
High
|
Unassigned | ||
Bug Description
Bug 61909 has gotten too cluttered/ignored, so I have opened a new bug.
We must fix the primary failure here: when the "security" check box is clicked, the security contact is NOT subscribed, but they should be. There is _no way_ in the LP UI[1] to search for bugs that are marked "security", and as such, security contacts must search for stuff their team is subscribed to. This needs to get fixed ASAP, as we are losing more and more bugs into this void.
| visibility: | private → public |
| Changed in malone: | |
| status: | New → Confirmed |
Revision history for this message
| Graham Binns (gmb) wrote | #1 |
| summary: |
- marking bug as "security" does not subscribe security contact + Marking an existing bug as "security" does not subscribe security + contact |
| Changed in malone: | |
| importance: | Undecided → High |
| status: | Confirmed → Triaged |
| security vulnerability: | yes → no |
To post a comment you must log in.
Sorry, I misunderstood... This is essentially an exact duplicate of bug 61909 (at least fixing that bug would fix this one and would only be a few lines of code extra).
In future, if you feel a bug's been ignored, please comment on it and, if necessary, bring it to the attention of an LP team member in #launchpad on Freenode.