private bugs and secret attachments
Bug #1954972 reported by
Seth Arnold
This bug affects 2 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Triaged
|
Low
|
Unassigned | ||
Bug Description
Hello, once in a while someone will post a bug with a coredump or includes credentials or other private data. I'd like to have a way to mark specific attachments as Must Remain Private, and forbid opening the bug to public until either that flag is removed or the attachment is removed. (Or something similar.)
I'd just like to have a Launchpad-provided reminded that some attachments should be deleted before flipping the bug to public.
Thanks
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| tags: | added: disclosure privacy |
Revision history for this message
| Jeff Lane (bladernr) wrote | #1 |
To post a comment you must log in.
I'd like this as well, we work with Hardware partners who file bugs on LP and we end up doing this dance between "File a private bug here, now create a public bug over here, now put your private files and comments in the first one but remember to put public-worthy comments and attachments in the second one" and that is always a confusing mess.
It would be helpful if LP had the same features as other bug trackers where individual comments and attachments could be marked private while the rest of the bug remained public.