Warn/Disallow commenting on fixed/closed bugs if the comment contains "re-open" or similar
Categories
(bugzilla.mozilla.org :: General, enhancement)
Tracking
()
People
(Reporter: standard8, Unassigned)
References
Details
I've just had a comment from a new-to-bugzilla person on a bug that was fixed in Firefox 68, which whilst similar, is highly unlikely to be the same issue, where they asked for the issue to be re-opened.
Since we very rarely re-open "Fixed" issues that have been landed for longer than the current release cycle, I'm wondering if we could do something like if new to bugzilla, and comment contains 're-open' => put up message to open a new bug.
We don't get these often, but it would help if these were straight-off filed as new issues.
We might need to make this slightly wider and catch any comment on an old fixed bug by a new person.
|
||
Comment 1•5 years ago
|
||
I think we should simply disallow new-to-Bugzilla users to comment on closed bugs unconditionally.
|
||
Comment 2•5 years ago
|
||
I think we should simply disallow new-to-Bugzilla users to comment on closed bugs unconditionally.
This has a lot of potential and I very much like the intention, plus guiding users to file bugs from old ones along the lines of bug 1196291 comment 1. We have plenty of recent examples of users asking "when is this going to be fixed", "what release", or "it's still not working for me". It would be SO nice not to have to deal with these. But many of these also come from not new users - and maybe that's a separate bug. That said, I'm not yet sold on the idea of unconditionally blocking feedback from new users in closed bugs.
Some questions:
- Are we talking about also blocking new users who are already cc: on the bug report?
- To prevent unnecessary new bugs from being filed and making equally more work, can we give hints like "The fix does not appear prior to version NN, which may not have yet shipped. If you are using version NN or newer please file a new bug."? (hopefully we can automatically provide the correct version # in the hint)
- What examples do we have where feedback IS wanted in a "fixed bug" report? From what types of users? Nightly users? Beta users?
- Is the criteria for "new-to-bugzilla" as currently defined too strict or is it too loose for this proposed use?
Perhaps public feedback should be solicited to get a more ideas for an initial implementation. Or CC more folks on this bug report
With the upcoming rules system for actions on bugs we can restrict the products components for which we block comment on a closed bugs.
So if the Thunderbird team want to exclude their products and components.
Product specification for rules system: https://docs.google.com/document/d/1KFZ7t15kEU-6DQsuSRoZrlUBeV6M2TqnedK2FNTXrhA/edit?usp=sharing
Bug for rules system: https://bugzilla.mozilla.org/show_bug.cgi?id=1524700
|
|
||
Comment 4•5 years ago
|
||
Thanks. But my concern has nothing to do with Thunderbird.
We should fix this by preventing all comments.
Description
•