Home

Issues Process

Issues progress through our teams and process as follows:

Creation of new issue

New issues are created from the templates for raising bugs or enhancement requests.

Provided fields in the template should be filled in.

A suggested priority should be set - the triage meeting should take this under advisement when setting the actual priority of the issue.

Triage

Development Manager & Product Manager meet regularly to review newly raised issues.

Labels to be set:

• Severity - from sev1-critical to sev5-trivial
• Priority - from p1-high to p3-low

Other labels wontfix, duplicate and invalid may be set at this time.

Development and fixing / implementation

The development team should generally work on issues in priority order, then severity order.

They should not work on issues labelled wontfix, duplicate or invalid.

Once an issue has been fixed / implemented, the resolved label should be set.

An issue can also be labelled wontfix, duplicate or invalid.

Testing and verification

Verification should be done on issues marked as resolved to check that they are fixed.

The test team should generally work on verifying issues in priority order, then severity order.

They should work on issues labelled resolved, wontfix, duplicate or invalid:

• resolved - ensure the issue has been fixed / implemented appropriately
• wontfix, duplicate or invalid - confirm whether they agree with the decision

If an issue has not been fixed / implemented, or the conclusion is disagreed with, unset the relevant label so that it is back with the development team.

If an issue has been fixed / implemented, close the issue.