Guildelines on Filing Issues

When filing an issue, project members should choose a priority and milestone. Here's what the priorities mean:

Here's the lifecycle of an issue:

1. A user reports an issue setting the priority and it has status New. If the reporter is a project member, they set a milestone.
2. The issue is triaged by a developer, if it was not originally entered and triaged at the same time. It may be rejected by setting its status to Invalid, WontFix, or Duplicate. Or, it may be Accepted.
3. If it is accepted, it may also be labeled to identify the part of the product affected or the nature of the cause of the problem.
4. The project owner may ask for more information and the initial reporter may add comments to provide that information.
5. The issue owner may set the status to Started.
6. Other users may provide additional comments that can help resolve the issue, or express their interest in having the issue resolved in a timely milestone.
7. If the original owner cannot work on the issue, or discovers that another project member would be a better person to work on the issue, it can be reassigned to another owner, or to no owner. Likewise, if work on the issue cannot be fit into a given milestone, the issue can be slipped by labeling it with a later milestone, or the milestone label can be removed altogether.
8. Once the development work has been done to resolve the issue, it's status can be set to Fixed.
9. Once the fix is deployed to a place it can it can be verified its status is changed to Fixed-in-QA or Fixed-in-dev depending on where it's been deployed.
10. The issue reporter or another team member verifies that the fix actually fixed the reported problem, and set the status to Verified once that has been done.
11. If verification fails, or if the original reporter adds a comment to say that the Fixed-in-X issue is still a problem, the issue can be set back to an open status.