Don't let people CLOSE bugs




19 years ago
6 years ago


(Reporter: Richard Zach, Assigned: justdave)





19 years ago
If I understand correctly, a bug
should only be CLOSED when it's been first RESOLVEd, then VERIFIED, and then the
product ships.  So probably not everyone should be able to mark a bug CLOSED.

Comment 1

19 years ago
I agree, it would be nice to have a feature similar to "Can confirm a bug" that 
would be called "Can close a bug".  This could be expanded to include "Can 
________ a bug" and insert whatever state a bug may be in.

In our QA process, only the person who opened the bug is allowed to close it, 
so perhaps something like this could be an option as well?

Comment 2

19 years ago is the new owner of Bugzilla and Bonsai.  (For details,
see my posting in netscape.public.mozilla.webtools,
news:// .)
Assignee: terry → tara

Comment 3

18 years ago
Bah. More and more people use "Closed" where they really mean "Verified". This
is partially an education thing, and partially a "mistake is easily made" thing.
By not making it possible for people to close the bug unless they are actually
allowed to close it you'd solve a lot of problems.

CC'ing per timeless' request.

Comment 4

18 years ago
This seems like a good idea to me too.  Maybe this option could even be disabled
in the bugzilla installation until Mozilla 1.0 begins to see the
light of day.
Add my vote.

Comment 6

18 years ago
also think this is a good idea
OS: Linux → All
Hardware: PC → All

Comment 7

18 years ago
Bug 49808 has a patch for this.  It doesn't seem to leave the options off of 
show_bug.cgi for users without the permissions, though.
Asa/DawnTara, what's the status on this?

Comment 9

18 years ago

we are getting more and more people helping out, and the number of closed bugs
is rising.  Another options would be a "unclose" bug button which would reset
the bug to the inital resolution.

Comment 10

18 years ago
It might be partly a `mistake is easily made' thing ... but the fact that
<> doesn't actually mention anything 
about shipping a product can't help.

Comment 11

18 years ago
mpt, it does.

QA has looked at the bug and the resolution and agrees that the appropriate
resolution has been taken. Bugs remain in this state until the product they were
reported against actually ships, at which point they become CLOSED.
i asked nearly a month ago, but never got a response: what's the status of this
issue? or, rather, when will this be fixed? how difficult could it be to make
the Close radio button only visible to people with the right privs? i guess it
[partially?] depends on when and whether the patch for bug 49808 is checked

thanks much!

Comment 13

18 years ago
Ok Asa, your turn to reopen bug 50174. :-) But I still think the resolution page 
should clarify the meaning of CLOSED in the CLOSED section itself.

Comment 14

18 years ago
So can someone explain what the rationale behind having CLOSED at all is, 
anyways?  It doesn't seem to be any more than VERIFIED.  And bugs that have 
been CLOSED are just as likely to get reopened as VERIFIED ones are. So what's 
up?  Is it just meant as a third level of QA (RESOLVED -> VERIFIED -> CLOSED) ?

Comment 15

18 years ago
It makes sense to do away with the option altogether. As Blake said, a bug can
just as easily regress after the product ships (bug marked CLOSED) as it is
before the product ships (bug marked VERIFIED). It seems that the CLOSED option
may just be redundant.

Comment 16

18 years ago
Where CLOSED would make sense is for RFE kinda bugs. I'd rather not people
reopen those because of a regression (since they'd have to change the bug from
"RFE implement foo" to "foo doesn't do bar any longer" anyway).
I think what Stephen says about CLOSED being unnecessary is true.

It should be up to the product team to check for regressions when the product
ships.  And whenever else they choose to.

And it would be nice if we didn't get the extra VERIFIED -> CLOSED notification.

That being said, CLOSED gives them an easy way to maintain a list of unchecked
bugs.  How can we provide that functionality in a better way?

Comment 18

18 years ago
just a comment. i think closed is fine as a state. it helps me determine easily 
determine the bugs which have been reopened due to customer response (reopen 
after a close) and those which have been caught in QA (reopen after 
resolved/fixed). this in turn helps me to oversee the effectiveness of our QA 
This may be more of a thing really -- should it be moved to the component? Asa?
Target Milestone: --- → Future

Comment 20

17 years ago

*** This bug has been marked as a duplicate of 49808 ***
Last Resolved: 17 years ago
Resolution: --- → DUPLICATE
moving to Bugzilla product
reassign to default owner/qa for INVALID/WONTFIX/WORKSFORME/DUPLICATE
Assignee: tara → justdave
Component: Bugzilla → Bugzilla-General
Product: Webtools → Bugzilla
Target Milestone: Future → ---
Version: other → unspecified

Comment 22

17 years ago
Verified dupe
QA Contact: matty_is_a_geek → default-qa
You need to log in before you can comment on or make changes to this bug.