Bugs:Tasks

There are a number of ways to start triaging:

Triage a single product (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). If you want to constantly be informed about any changes, set up user watching by adding the "QA Default Contact" email address to your "User Watching" list.

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.

Update reports of older versions
Take a look at old bug reports and try to reproduce them with the latest software release to find out whether the reports are still valid. If they have been fixed in the meantime, you can set them to RESOLVED FIXED and set the Target Milestone to the version that works fine, plus adding a comment about it. List of open reports for Maemo version 4.1 or earlier.

Clean up reports that need more information
Clean up bugs with moreinfo keyword that have not been changed for 6 months. This means that more information had been requested from the reporter but has not been provided. These bugs should be closed as WORKSFORME if you are not able to reproduce. If there is simply not enough information to be a useful report, then close the bug as INVALID. Please always explain your decision by adding a nice comment and in the latter case, ask the reporter to provide the information asked for, if he can, and reopen the bug. The Greasemonkey triage helper script can help you here.