Bug management/Triage tasks

There are a number of ways to start triaging:

Triage a single application
Pick up the product or component that interest you, or which you know about, or are willing to learn, or happen to use. You can query for existing open reports and take a look at issues that interest you, for example in order to update them by updating the Version field, or noting that they have been already fixed in the version you use (please mention the exact version that you use in a comment, also see the section on reproducing in the Triage Guide).

Triage the Extensions category
Wikimedia Bugzilla hosts many extensions that are developed by volunteers. Their maintainers are always happy about a helping hand. The steps explained in "Triage a single application" also apply here. You can explicitly search for bug reports on applications in Extensions by setting the product to "MediaWiki extensions" on Bugzilla's query page.

Triage the latest incoming reports
Take a look at the latest incoming reports of the last two weeks and try to reproduce them, or ask for missing information, or add additional information. See the Triage Guide.

Try to reproduce reports that are UNCONFIRMED
Many reported problems cannot be easily reproduced. Take a look at bug reports in UNCONFIRMED state, try to reproduce them, and feel free to add a comment either with instructions to reproduce or that you could not reproduce it and mention the version that you use. Please do not add such comments for reports in NEW status though.

Update reports of older versions
Take a look at old bug reports and try to reproduce them with the latest software version to find out whether the reports are still valid. If they have been fixed in the meantime, you can set their status to RESOLVED FIXED and add a comment in which version or on which Wikimedia website you could not reproduce the problem anymore. List of open reports that have not seen any changes in the last 18 months.

Retest reports with the "testme" keyword
Some reports have been marked with the testme keyword. You can find these reports here. Retest them if possible, and remove the keyword and add information about your setup in case that you succeed.

Update your own reports
Most of us have submitted bugs in the past and forgotten about them. Take a look at them and check whether they still apply in the latest software version. Go to the Query website and make sure that under "Status" UNCONFIRMED, NEW, ASSIGNED and REOPENED are checked. Under "Email and Numbering", enable "the reporter" and enter your email address below in the text field.

Update reports for a specific browser
You could try to retest older tickets that reportedly only happened in a specific browser if you use that browser, maybe in the same or a newer version. Please always mention which exact browser and version you run.

Lists of open bug reports specifically for: Apple Safari | Firefox | Google Chrome | Internet Explorer | Opera

Update reports on mobile platforms
You could try to retest older tickets that reportedly happened on a specific mobile platform, for example if they still happen in the same or in a newer version of that platform. Please always mention which exact version and hardware you run when updating a report.

Lists of open bug reports specifically for: Android | iOS | Windows Phone | Firefox OS | Blackberry

Clean up reports that have never seen an answer
There are any open bug reports that have never received a response. Many need triaging, and for older ones you could try to reproduce them.
 * List of all open bug reports that are not enhancement requests and are without a response.
 * List of all open reports without a response.
 * Both queries above currently do not work. A workaround to find some of them might be to query for open bug reports that are not enhancement requests and only have one (initial) comment.

Sync upstream and downstream reports
This is a cumbersome task that asks for automation but as long as nothing is in place it needs to be done sometimes: Query for bug reports that have a non-empty "See Also" field and include the "upstream" keyword.

Sync Gerrit status of patches with related bug reports
Sometimes patches to fix a bug report get merged in Gerrit but the bug report remains open, so after carefully reading the comments in the bug report and getting an impression of the status and if really all patches have been merged in Gerrit, you could ask the developers in the bug report if the bug report should still stay open.

Open bug reports in PATCH_TO_REVIEW status that have a "merged by jenkins-bot" comment

Further links
If you feel like going from triaging to writing code there are annoying little bugs available.