This design feature obviously leads to problems for security related bug attachments ;)
Seems that we should
- describe more clearly that simply removing a bug attachment does not automatically delete the Librarian file
- add an option to reliably delete the librarian file of a bug attachment. Such an option should probably only available to people with sufficient privileges, like a project owner or a driver.
A form allowing the latter should display something like:
This file is also referenced as
* a bug attachment of bug 1234
* a logo for projext X
* ....
are you sure that you want to completely delete this file?
(OK, having a librarian file both as a bug attachment and as a logo is not very likely, but Launchpad references LFAs from 43 different tables; I can't come up quickly with a better example...)
This design feature obviously leads to problems for security related bug attachments ;)
Seems that we should
- describe more clearly that simply removing a bug attachment does not automatically delete the Librarian file
- add an option to reliably delete the librarian file of a bug attachment. Such an option should probably only available to people with sufficient privileges, like a project owner or a driver.
A form allowing the latter should display something like:
This file is also referenced as
* a bug attachment of bug 1234
* a logo for projext X
* ....
are you sure that you want to completely delete this file?
(OK, having a librarian file both as a bug attachment and as a logo is not very likely, but Launchpad references LFAs from 43 different tables; I can't come up quickly with a better example...)