Last updated January 18, 2012.
Triage is a protocol used to rapidly diagnose in first aid to separate wounded people in groups so doctors can focus on patients with the best options to be cured. This page is a starter to try to help module maintainers (and people making issues) to have an organized prioritized list.
Doing a triage on a particular issue queue relieves the developer from tracking all issues in their queue. It helps identifying bugs as real bugs. Almost everybody able to configure a particular Drupal module should be able to apply.
Doing a triage
Doing a triage is initiated when an issue is submitted. The triage team validate the issue and route it accordingly.
A triage member needs to:
- understand the Issue Status and transitions.
- find issues to triage
- find duplicate issues
- find issues with timed response needed
- have a list of Stock Responses.
Postmortem
When a project exists for a while issues are slipped through the developers attention. Probably most of these issues are support request, bugs already fixed or ...
For clearing these issues we need a postmortem process.
States
More information
- Issue Triage groups page where all aspects of triage are being discussed.
- Gnome Triage Guide
Note: comments below are standard answers that will be incorporated in the protocol and should be moved to Stock Responses
| Attachment | Size |
|---|---|
| triage.dot_.txt | 2.21 KB |
| triage.png | 84.97 KB |
Comments
Will be fixed in Views 3.x
This issue can be closed because it will most likely be fixed in in Views 3.x.
Please reopen if you disagree on this or are still experiencing problems.
--triage-ddd-nl
Small problem. Workaround available
This issue can be closed because it will most likely not going to be fixed. The reporter provided a workaround which kind of solves the problem.
Please reopen if you disagree on this or are still experiencing problems.
--triage-ddd-nl
Support request. Answered. Reporters seems to have lost interest
This issue can be closed because the support question has been answered, but the reporter did not reply anymore.
Please reopen if you disagree on this or are still experiencing problems.
--triage-ddd-nl
Won't fix
This issue can be closed because it will most likely never be fixed.
Please reopen if you disagree on this.
--triage-ddd-nl
How to triage old issues?
When the maintainer touched the issue evaluate the maintainers response and decide on that.
- patch? (see other comments)
- won't fix?
No activity but probably valid issue
Is there likely going to be any more activity on this issue? Please update this issue.
--triage-ddd-nl
We need to validate this page
We need to validate this page with Status settings for an issue too.
No activity
No activity for a very long time. Set to won't fix.
--triage-ddd-nl
Such comment does not explain
Such comment does not explain why the issue status was changed. Some explanation and words on what to do when the issue is still valid (people are waiting or working on solutions) would make the response more friendly.
State transitions in the diagram are wrong
There's only one auto-2-week transition: from "fixed" to "closed (fixed)". None of the other closed status options automatically transition to another. In theory, once an issue hits any of the "closed (*)" states, it never moves again.
__________________________________________________________________
My professional services are available through 3281d Consulting