UbuCon - How to Triage Bugs

Most of what you would want to know about Bug Jams could be found here: https://wiki.ubuntu.com/Jams/Bugs

We did more of a quick session on how to get started with Triaging Bugs. When users report issues with applications on a bug tracker, sometimes they are not assigned to the right package or team, or they are unverified. Triaging bugs is the act of getting those bugs into the hands of the developers by doing a couple of key things. 1. Evaluate the bug and if necessary assign the right package. Then read the bug summary and ensure that as much information as possible is available things like the ouput from the following commands:

lspci -vv
uname -a
cat /etc/*release
aptitude show

Other specific types of issues may need a little more specific info, but we can't expect for new users and apport to give us everything we need. So if you read the bug and the info is missing and there is no package assigned, you can assign it a package and change the status from new, to incomplete since it's lacking info. If you are running the same versions and they bug requester listed the steps to duplicate the issue, you can attempt to follow along and see if you also have the same results. In that case you could mark the bug confirmed. When you assign the package the developers that work on the package are notified, and when you confirm they see that too. All of this is in effort to try and provide as much info for the developers and weed out some issues that are not affecting everyone.

I hope that this isn't confusing, but a couple of links off that wiki that I gave you earlier and you can find out a lot more in detail.