-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Issues progress through our teams and process as follows:
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.
Development Manager & Product Manager meet regularly to review newly raised issues.
Labels to be set:
- Severity - from
sev1-critical
tosev5-trivial
- Priority - from
p1-high
top3-low
Other labels wontfix
, duplicate
and invalid
may be set at this time.
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
.
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
orinvalid
- 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.