After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 327816 - reopen on new comment for needinfo&reporter is not nice
reopen on new comment for needinfo&reporter is not nice
Status: RESOLVED FIXED
Product: bugzilla.gnome.org
Classification: Infrastructure
Component: general
unspecified
Other Linux
: Normal major
: ---
Assigned To: Bugzilla Maintainers
Bugzilla Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-20 08:58 UTC by Sebastien Bacher
Modified: 2006-04-12 02:58 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Sebastien Bacher 2006-01-20 08:58:08 UTC
The new "reopen on new comments" behaviour is quite annoying. Lot of people comment to ask how to install debug package, to say they will do, to say they don't have it for now but will comment when they get the bug again, etc. I think it's easier to reopen bugs when you get useful details than switching again and again stuff to NEEDINFO. 

Could we get the previous behaviour? :)
Comment 1 Baptiste Mille-Mathias 2006-01-20 09:00:46 UTC
Stupid proposition : a checkbox "Reopen this bug" not ticked by default for closed bug ?
Comment 2 Olav Vitters 2006-01-20 09:14:35 UTC
Baptitste: It is only set to reopen when the reporter looks at the bug and the status is set to NEEDINFO. Will be 'Leave as NEEDINFO' for everyone else.
Comment 3 Elijah Newren 2006-01-21 20:26:57 UTC
Actually, despite being one of the huge proponents of the current behavior, I'm finding it somewhat irritating as well.  The old behavior also sucks because it means bugs lost in the needinfo state for forever, so let's not go back to that.  How about something different:

For persons other than a developer of the product, unselect knob (the status).  Fix our assume-user-meant-to-make-no-status change assumption in process_bug for bugs in the needinfo state and instead throw up a warning asking the user to pick the new status (either like reassigning does currently, or perhaps telling them to go back to the bug and select the status)

I think that or some modification of it (suggestions, anyone?) would be a better compromise than just reverting to the previous behavior without the current annoyance of having to remark a bug needinfo 20 trillion times.
Comment 4 Sebastien Bacher 2006-01-21 21:57:33 UTC
Unselecting it by default and having a page like the reassing one seems a good compromise
Comment 5 Elijah Newren 2006-04-12 02:58:44 UTC
I added an extra "Ask me whether to reopen" knob, which is selected for needinfo bugs.  That way, users can manually specify whether to leave the bug as needinfo or reopen it if they want to avoid the extra question, but if they don't, they'll get the extra question.  :)

2006-04-11  Elijah Newren  <newren gmail com>

	Don't default to reopening NEEDINFO bugs.  It was freakin'
	annoying.  Don't revert to the old behavior of leaving them closed
	either -- that caused bugs to be lost.  Instead, default to
	querying the user what to do (though they can manually specify to
	avoid the extra question).  Fixes #327816.