Secrecy settings for attachments
Bug #512085 reported by
Jonathan Thomas
This bug affects 6 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Launchpad itself |
Won't Fix
|
Low
|
Unassigned | ||
Bug Description
It would be neat if attachments to bugs could be marked private. This way, apport crashes could have the potentially-
See also bug 39674.
| Changed in launchpad: | |
| status: | New → Triaged |
| importance: | Undecided → Low |
| affects: | launchpad → malone |
| tags: | added: privacy |
| description: | updated |
Revision history for this message
| Robert Collins (lifeless) wrote | #1 |
| Changed in launchpad: | |
| status: | Triaged → Won't Fix |
To post a comment you must log in.
We've found that users are very poor at separating out information. If we have public and private attachments on one bug, its almost certain someone will paste unredacted content from a secret attachment onto the bug, thereby defeating the private setting on it - and the UI for individual attachments is much narrow than for the entire bug so its going to be harder to get it right there.
Accordingly, I think this would be a misfeature, it would encourage something we want to avoid. The upcoming bug linking feature may address the source of your complaint - that bugs with a public oot cause end up private because of the data needed to analyse them. (Using a dependency bug will let this be pretty clean).