Bugmasters/Bug days/mentored: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
Line 54: Line 54:
The same [https://bugzilla.mozilla.org/report.cgi?x_axis_field=bug_status&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Boot2Gecko&product=Bugzilla&product=bugzilla.mozilla.org&product=Calendar&product=Community+Tools&product=Core&product=Developer+Documentation&product=Firefox&product=Firefox+for+Android&product=Firefox+for+Metro&product=Mozilla+Developer+Network&product=Mozilla+Localizations&product=Mozilla+QA&product=SeaMonkey&product=Socorro&product=support.mozilla.org&product=Testing&product=Thunderbird&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=2000-01-01&chfieldto=2013-02-01&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap good first bug report on Bugzilla], where each number is linked to a query.
The same [https://bugzilla.mozilla.org/report.cgi?x_axis_field=bug_status&y_axis_field=product&z_axis_field=&query_format=report-table&short_desc_type=allwordssubstr&short_desc=&product=Boot2Gecko&product=Bugzilla&product=bugzilla.mozilla.org&product=Calendar&product=Community+Tools&product=Core&product=Developer+Documentation&product=Firefox&product=Firefox+for+Android&product=Firefox+for+Metro&product=Mozilla+Developer+Network&product=Mozilla+Localizations&product=Mozilla+QA&product=SeaMonkey&product=Socorro&product=support.mozilla.org&product=Testing&product=Thunderbird&bug_status=UNCONFIRMED&bug_status=NEW&bug_status=ASSIGNED&bug_status=REOPENED&resolution=---&longdesc_type=allwordssubstr&longdesc=&bug_file_loc_type=allwordssubstr&bug_file_loc=&status_whiteboard_type=allwordssubstr&status_whiteboard=good+first+bug&keywords_type=allwords&keywords=&bug_id=&bug_id_type=anyexact&votes=&votes_type=greaterthaneq&emailtype1=substring&email1=&emailtype2=substring&email2=&emailtype3=substring&email3=&chfieldvalue=&chfieldfrom=2000-01-01&chfieldto=2013-02-01&j_top=AND&f1=noop&o1=noop&v1=&format=table&action=wrap good first bug report on Bugzilla], where each number is linked to a query.


<onlyinclude>
<bugzilla>
{
      "product":      ["Core","Calendar","Toolkit","Firefox", "Boot2Gecko", "Testing","Thunderbird", "SeaMonkey"],
        "whiteboard":    "good first bug",
        "status":["NEW","REOPENED"],
        "include_fields": "id, product, summary, status, whiteboard, last_change_time"
}
</bugzilla>
</onlyinclude>


Current bugs marked with "mentor" field
Current bugs marked with "mentor" field
<bugzilla type="count" display="bar">
<bugzilla type="count" display="bar">
     {
     {

Revision as of 07:15, 31 July 2013

Triaging mentored and good first bugs

What we'll do

  • Pick a query - click on it to open up a list of bugs!
  • Sort the query you're looking at by last changed date.
  • Look through the oldest bugs first.
  • Ask assignees or mentors for more info if you need information from them.
  • Unassign bugs, remove good first bug or mentored tags if responses show that's what's needed.
  • Ask on irc on #bugmasters if you're not sure what to do on a bug!

Sign up to triage one of these!

This Bugzilla report shows the [good first bug] not touched upto 2013-02-01

Core

Firefox

Toolkit

Thunderbird

Calendar

Clearing older bugs

  • Check bugs that were triaged in the past, and have an open needinfo: [1]
    • For these bugs, if there hasn't been any response from a needinfo, you should ask someone else, either the bug mentor or some other developer on a relevant team.
    • You may want to set the bug assignee back to nobody@mozilla.org, so that a new person can take the bug.

Goals

  • One of the goals of rummaging through these bugs is to make sure the list of bugs is current.
  • Another goal is to see if unassigning inactive bugs is helpful, as it may "free" the bug for a new person to work on it.

Status

Current New bugs tagged as [good first bug] with status NEW or REOPENED

Bugzilla query error

Invalid type (count) and display (table) combination1


The same good first bug report on Bugzilla, where each number is linked to a query.


Current bugs marked with "mentor" field

Bugzilla query error

Invalid type (count) and display (table) combination1