Open Bug 1196291 Opened 5 years ago Updated 1 year ago

Close untouched closed bugs for comments from users without editbugs, and place an explanation plus a link to something like "clone this bug" UI

Categories

(bugzilla.mozilla.org :: Bug Creation/Editing, enhancement)

Production
enhancement
Not set

Tracking

()

People

(Reporter: Gijs, Unassigned)

References

Details

(Keywords: ux-error-prevention)

See http://www.gijsk.com/blog/2015/08/why-you-might-be-asked-to-file-a-new-bugissue-instead-of-commenting-on-old-ones/ .

It would be nice if bugzilla helped avoid this by making it easy for people to file a new bug instead, and gathering the same data we get from new bugs (UA, detailed steps to reproduce).
(...continuing from IRC...)

It's also a useful self-triage mechanism. If a user has found a bug close to their existing issues, we can use that to help them file a new bug in the right spot automagically.

We might want to have a grace-period involved, to allow commenting on recently-closed bugs. I'm mostly saddened by this happening in old bugs, where users are basically talking to an empty room. But Gijs' points are still valid no matter what the age. And, really, if it's simple and painless to get a new bug filed, everyone still wins.

I was also thinking about cases where there's still ongoing activity / discussion / concerns in the bug, even though it's closed. But the more I think about it, the more I'm starting to think even that might be best to bump to a followup bug.
Perhaps with a checkbox to comment on the old bug?

"I filed a followup: bug <N>, <summary>"
Assignee: nobody → glob
Summary: Close untouched closed bugs for comments from users without canconfirm/editbugs, and place an explanation plus a link to something like "clone this bug" UI → Close untouched closed bugs for comments from users without editbugs, and place an explanation plus a link to something like "clone this bug" UI
Assignee: glob → nobody
Type: defect → enhancement
You need to log in before you can comment on or make changes to this bug.