MozillaWiki

Bug Wrangling Projects: Difference between revisions

Page Discussion

Bug Wrangling Projects (view source)

Revision as of 17:51, 22 April 2013

2,646 bytes removed ,  22 April 2013
m
added redirect to the right page
mNo edit summary
m (added redirect to the right page)
Line 1: Line 1:
Here are some ongoing Bugmaster projects to help manage Mozilla bugs.  Each one will have bug days or events occasionally, to help its contributors communicate and work together.  "Triaging" a bug can mean a lot of different things.
#REDIRECT [[https://wiki.mozilla.org/Bugmasters/Projects]]
 
==UNCONFIRMED Triage==
* [https://bugzilla.mozilla.org/buglist.cgi?list_id=6184146&resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=[Bug%20creation]&query_format=advanced&chfieldfrom=-60d&bug_status=UNCONFIRMED&component=Untriaged&product=Firefox Latest Untriaged Firefox bugs], UNCONFIRMED, from the last 60 days.
 
(Add tips on how to triage these)
 
==Incoming==
[https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Today%27s%20UNCO%20Bugs&list_id=6184210 Bugs Filed Today]. All bugs filed in the last 24 hours.  Usually this is around 400 bugs, but the number fluctuates over the course of the day.
 
To work in this area, go through the bugs with status UNCONFIRMED.
** [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=runnamed&namedcmd=Today%27s%20UNCO%20Bugs&list_id=6184175 Today's UNCO Bugs]
** If you can reproduce a bug, and are fairly sure it is a Mozilla bug, mark it NEW.
** Assign the bug into a product and component, or tag it needs-component
** Tag the bug with other triage tasks that may be needed.
 
 
==Websites==
This is for bugs that have been reported in Mozilla-run websites.
 
* Take a look at the [https://bugzilla.mozilla.org/buglist.cgi?list_id=6185685&resolution=---&resolution=DUPLICATE&query_format=advanced&bug_status=UNCONFIRMED&product=Websites Website UNCONFIRMED] bugs.
* Sort on Status, ID, or another field.
* Check to see that the bug still exists.
** If you can't reproduce it, ask the reporter, in a comment with a need-info flag, if they can reproduce it.
*** If they can't, or don't answer after a week or so, resolve the bug as WORKSFORME.
** If you can reproduce it, mark it NEW and leave a comment to describe what you did. You may be able to find a person to cc on the bug if you look for who has resolved past, similar bugs.
 
* Websites bugs marked NEW can also use triaging! Here's a bugzilla query for [https://bugzilla.mozilla.org/buglist.cgi?list_id=6185727&resolution=---&resolution=DUPLICATE&chfieldto=Now&chfield=[Bug%20creation]&query_format=advanced&chfieldfrom=-1y&bug_status=NEW&product=Websites Website NEW bugs reported within the last year].
 
==Accessibility==
This is for bug wranglers who would like to help accessibility developers and end users.
 
* Join #bugmasters and #accessibility
 
* Meta bug cleanup: this is a very easy task for beginners!
** Look at accessibility meta bugs
** Pick one, search for other bugs that are missing, and add them to the meta bug
Lizhenry
Confirmed users
2,816

edits

Retrieved from "https://wiki.allizom.org/Special:MobileDiff/648519"