Talk:Bug management/Bug report life cycle

Jump to navigation Jump to search


Some people seem to use UNCONFIRMED to mean "Maybe we should WONTFIX this". Isn't UNCONFIRMED supposed to be used only for situations in which no one has been able thus far to reproduce the complained-about problem, but also the results of experimentation haven't yet made it seem unlikely that anyone will be able to reproduce it by the steps described in the bug report? Leucosticte (talk) 06:25, 2 January 2014 (UTC)

I don't have a strong opinion here. UNCONFIRMED seems to be also used for "I am not convinced that this is a valid request" sometimes, which is close to "I cannot confirm that this is valid" to me. --AKlapper (WMF) (talk) 09:21, 2 January 2014 (UTC)
Yeah, it seems like a good definition would be "possibly INVALID". Leucosticte (talk) 16:29, 1 September 2014 (UTC)


The definition of invalid here seems to imply upstream issues are invalid, which they usually aren't considered as such. Bawolff (talk) 06:04, 29 January 2014 (UTC)

“Upstream” is also a way to say “out of scope of the project”. So I think it is consistent with the other invalid cases. --Danwe (talk) 17:00, 26 April 2017 (UTC)

Duplicate and Verified[edit]

When I edit a task, the only statuses available to me in the dropdown are: Open, Resolved, Stalled, Declined, and Invalid. Do you know why my list is different from what is documented on this page? --KSmith (WMF) (talk) 17:02, 20 May 2015 (UTC)

@KSmith (WMF): "Verified" is a project (meh, the page says "keyword"). It's only mentioned because it was a status in Bugzilla. You cannot set the status duplicate (as that would not create any connection to the master task), instead you have to "merge duplicates in" and define the number of the duplicate task. --AKlapper (WMF) (talk) 18:35, 20 May 2015 (UTC)