Invalidating bug report that's open elsewhere sends alarming notification

Bug #204082 reported by Matthew Paul Thomas
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Launchpad itself
Triaged
Low
Unassigned

Bug Description

Sometimes bug reports are filed under the wrong context. Sometimes the correct context is added and the wrong context is marked "Invalid" or "Won't Fix", instead of the context being changed directly. This is partly the fault of bug 59389, and partly the fault of bug 80902, but not entirely; even once those bugs are fixed, some people will still refile bug reports the slow way.

When this happens, the mail notification sent out can be alarming to the bug reporter and other vested subscribers. All they see is that the bug report has been marked Invalid or Won't Fix; they do not see that the report is open elsewhere. For one example of this see bug 203286, but I've seen it happen several times.

One way of fixing this would be, whenever a bug report is marked as Invalid or Won't Fix in one or more contexts while remaining open in one or more other contexts, to mention those other contexts in the mail notification. Something like: "The report is still open in X."

Another way of fixing it would be for mail notifications to always show the status of the bug report in all contexts, whenever its status changes in any context.

description: updated
Curtis Hovey (sinzui)
Changed in malone:
status: New → Triaged
importance: Undecided → Low
tags: added: feature
Graham Binns (gmb)
tags: added: story-better-bug-notification
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.