Last modified: 2011-06-22 20:15:40 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T30121, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 28121 - Remove "CLOSED" status
Remove "CLOSED" status
Status: VERIFIED FIXED
Product: Wikimedia
Classification: Unclassified
Bugzilla (Other open bugs)
unspecified
All All
: Normal enhancement (vote)
: ---
Assigned To: Priyanka Dhanda
:
Depends on:
Blocks:
  Show dependency tree / graph
 
Reported: 2011-03-19 19:55 UTC by Krinkle
Modified: 2011-06-22 20:15 UTC (History)
5 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Krinkle 2011-03-19 19:55:13 UTC 
It's not part of our bug-lifecycle and so far I haven't found a use case for it (only confusing or wrong ones that complicate our search queries).

How about removing it from the options ?

One case where it was used [1] when a fixed bug was re-opened to request something else (invalid reopeneing). I think setting status back to RESOLVED,FIXED is more appropiate in such case.

Another popular use bugs that were marked as "DUPLICATE" before 2006.

And a third use was a work-around when creating buglists/advanced searches to exclude certain bugs that are marked as resolved but shouldn't be in there and where thus marked as CLOSED.
This can now be done by using "-----" as filter value for the resolution-field. That will list all pending/open bugs (whether new, assigned or reopened, and will not include duplicates).


If there are no use cases for it anymore, I think we should deprecate it in our workflow. Any comments ?

--
Krinkle

[1] https://bugzilla.wikimedia.org/buglist.cgi?query_format=advanced&bug_status=CLOSED&product=MediaWiki&product=MediaWiki%20extensions&product=Wikimedia
Comment 1 Bawolff (Brian Wolff) 2011-03-19 19:57:45 UTC 
I think
Comment 2 Bawolff (Brian Wolff) 2011-03-19 20:02:15 UTC 
Sorry, accidentally hit submit.


(Since I'm commenting to explain why I wrote "I think" above anyways, I might as well add a rather useless +1. The closed status always seemed purposeless to me).

I think the Calcey QA people used it to verify bugs were really fixed, but I don't see why we can't use re-open when they're not.
Comment 3 Antoine "hashar" Musso (WMF) 2011-03-19 20:10:09 UTC 
Too me, a RESOLVED bug is pending verification hence the VERIFIED status that could be made by someone actually testing the code or by the bug submitter.

Once deployed live / released, we could mark it as CLOSED much like we would say "let s forget about it".

If we do not want to use the purposed lifecycle, we can just remove VERIFIED and CLOSED statuses.

Also have a look at http://www.bugzilla.org/docs/tip/en/html/lifecycle.html
Comment 4 p858snake 2011-06-21 23:26:26 UTC 
Marking fixed, both closed and verified have been disabled (by chad i think?).
Comment 5 Antoine "hashar" Musso (WMF) 2011-06-22 20:15:40 UTC 
CLOSED disappeared, VERIFIED is still around though.

Marking bug as VERIFIED :)
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links