+patches page should allow removal of bugs

[Robert Collins]

A patch which isn't useful makes the bug show up in +patches indefinitely, this is a real nuisance. It should be possible to say 'this patch is not right' and wait for a new one to bring the bug back into +patches.

I'm sure this is sort-of a duplicate with some of the other +patches requested work, but I'm not entirely sure if it is as hard as those other features. I have in mind a simple 'zap the flag' to cause the bug to not show up, and the next new attachment would readadd it, or something.

[Deryck Hodge (deryck)]

I'm not sure we should worry about exposing this sort of functionality in the UI until we have some general batch editing capabilities for bug lists. I do agree this would be a nice to have -- i.e. a little "not a fix" button or checkbox which then toggles the "this attachment is a patch" flag on the attachment. Obviously, this could become more sophisticated if/when we work on a patch-branch-mergeproposal workflow.

[Deryck Hodge (deryck)]

Bug #345577 represents the patch-to-branch workflow request.

[Robert Collins (lifeless)]

Well, I can't set the priorities obviously. However right now there is:
 - something launchpad models
 - which affects users, particular maintainers of projects
 - which can be wrong
 - and which they can't fix

Thats pretty unpleasant for the user and likely leaves them feeling
frustrated and unhappy.

I recognise we can't do everything at once, but even if there was a
delete link for the patch status on the bug page itself, folk could
garden things.

One isn't going to mass-assess bug patches to see if they are right or
wrong, its going to be a bug by bug thing.