Bug 902617

Summary:	Red banner: "You need to specify a COMMENT when changing from RESOLVED to VERIFIED."
Product:	[openSUSE] openSUSE.org	Reporter:	Tony Mechelynck <antoine.mechelynck>
Component:	Bugzilla	Assignee:	Forgotten User At6q7iYYxC <forgotten_At6q7iYYxC>
Status:	RESOLVED WONTFIX	QA Contact:	Forgotten User lHgm-a2Axa <forgotten_lHgm-a2Axa>
Severity:	Normal
Priority:	P5 - None	CC:	forgotten_At6q7iYYxC, wolfgang
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:
Found By:	Community User	Services Priority:
Business Priority:		Blocker:	---
Marketing QA Status:	---	IT Deployment:	---

Description Tony Mechelynck 2014-10-25 12:54:28 UTC

Reproducible: Every time.

Steps to reproduce:
1. Browse to a RESOLVED bug. (You should be that bug's Reporter, or have Editbugs privileges — or both.)
2. Try to set it to VERIFIED without a comment.

Actual result: You can't (Red banner, see Summary).

Expected result: You should be able to; at most after an "Are you sure?" prompt.

Additional info: see bug 898061 comment #7 (and the bug history for #6 and #7) for a case where this requirement was particularly ludicrous.

Comment 1 Tony Mechelynck 2014-10-25 13:18:16 UTC

P.S. Another example of VERIFIED (IMHO) not needing a comment would be if a bug had been RESOLVED DUPLICATE, and the reporter wanted to express agreement with the dupe.

Comment 2 Tony Mechelynck 2014-10-25 13:44:10 UTC

P.P.S. Maybe this reaction of mine is what results from interacting with several subtly different Bugzilla installations — in my case, mostly the openSUSE Bugzilla and the Mozilla Bugzilla.

The latter now has an "inline changes" extensions which makes it redundant to record in a comment the mere change of a bug's Status. Now that I think of it, I remember that before it existed, there used to be comments saying nothing more than "=> VERIFIED" in cases similar to those mentioned in comment #1 and in bug 898061 comment #7.

If you decide to set this bug WONTFIX, I won't oppose such a decision, but please consider applying (if possible) to this Bugzilla the inline-changes extension currently in use at bugzilla.mozilla.org instead.

Adding CC to WolfiR who is very active at Mozilla too.

Comment 3 Forgotten User At6q7iYYxC 2014-10-27 13:31:00 UTC

The reason as to why we require a comment when going from RESOLVED to VERIFIED, at least at this time, is because both status are generally handled by different users: the RESOLVED by either the assignee or QA contact, and VERIFIED by either the QA contact or the reporter. By requiring a comment for each of these transitions, the product developers and managers can easily audit whether the bug solution satisfied the requirements. I will not, however, close this bug until I've had the chance to discuss this possibility with the team.

As for inline changes on BMO, this is currently in the process of being cleaned of any Mozilla-specific customizations by the Bugzilla developers (which include myself) for use as either an extension to Bugzilla or part of the core code in an upcoming release. I find it very useful nonetheless, and would love to bring it to our configuration once it is "production-ready"

Comment 4 Forgotten User At6q7iYYxC 2014-11-24 15:16:43 UTC

Resolving as WONTFIX. As soon as the BMO created 'inline changes' extension is cleaned up for general use, I will discuss bringing the changes to our Bugzilla with the core team.