How to triage OpenStack bugs

These are the bug triaging tasks, in descending order of priority. You should try to complete one before going to the next. It's quite difficult to reach the bottom of the list !

Priority 1: Triage new bugs

When someone files a bug, its state is set to New. The most important step in bug triaging is to provide feedback on that bug and make sure it's prioritized correctly.

List at: https://bugs.launchpad.net/openstack/+bugs?field.status=NEW&field.importance=UNDECIDED (replace openstack in URL with a specific project to get a project-only list)

Graph for: Nova, Glance, Swift

If the bug description is incomplete or the report is lacking the information necessary to reproduce the issue, you should ask the reporter to provide missing information, and set the bug status to Incomplete
If the bug report contains enough information, you should set priority to:
- Critical if the bug prevents a key feature from working properly (regression) for all users (or without a simple workaround) or result in data loss
- High if the bug prevents a key feature from working properly for some users (or with a workaround)
- Medium if the bug prevents a secondary feature from working properly
- Low if the bug is mostly cosmetic
- Wishlist if the bug is not really a bug, but rather a welcome change in behavior
If the bug has security implications, you should set the security flag (under "This report is public" on the top right)
If the bug affects a given subteam, you should set the appropriate tag (for example "ec2" for EC2 API issues)
Set the bug status to Confirmed
If the bug contains the solution, or a patch, set the bug status to Triaged
If the bug is likely to be quite easy to solve, add the low-hanging-fruit tag

Priority 2: Solve inconsistencies

Some bugs might end up in an incorrect state. You should fix:

Confirmed bugs with Undecided priority: priority should be set (see above)
New bugs with a priority set: status should be set to Confirmed (or In progress if an assignee is set)
In progress bugs without an assignee: an assignee should bet set, or the bug should return to Confirmed status

Priority 3: Review incomplete bugs

List at: https://bugs.launchpad.net/openstack/+bugs?field.status%3Alist=INCOMPLETE_WITH_RESPONSE&field.status%3Alist=INCOMPLETE_WITHOUT_RESPONSE

If the reporter provided the requested answer: bug status should be set to Confirmed
If the reporter did provide information, but more detail is required: ask for missing information
If the reporter did not answer within 2 weeks: Politely remind the reporter to provide missing information, for example:

We cannot solve the issue you reported without more information. Could you please provide the requested information ?

If the reporter did not answer the reminder for another 4 weeks: Set the bug status to Invalid with a comment, for example:

This bug lacks the necessary information to effectively reproduce and fix it, therefore it has been closed. Feel free to reopen the bug by providing the requested information and set the bug status back to ''New''.

Priority 4: Review stale In Progress bugs

Make sure In Progress bugs are actually in progress.

List: a tool will be provided to identify those bugs.

Priority 5: Review bugs with a patch

Some bugs are filed with an attached patch. We should review if the patch looks indeed like a patch, and if yes, set the bug status to Triaged to show that it comes with a likely solution, ready to be implemented.

List: https://bugs.launchpad.net/openstack/+bugs?field.status%3Alist=CONFIRMED&field.status%3Alist=TRIAGED&field.status%3Alist=INPROGRESS&field.has_patch=on