-
Notifications
You must be signed in to change notification settings - Fork 30
Issue management
Bugs should be added to the Bugs project in the "Triage" column. Bugs should sit in the Triage column until someone can reproduce the bug and provide reproduction instructions, at which point they should move to the "Reproduced" column. Assignee in the "Triage" column indicates intent to reproduce the bug.
Developers wanting to help out can pick up bugs from either the Triage or Reproduced columns, but should be aware that the Reproduced column is probably going to have more information about the issue at hand. Assignee in the "Reproduced" column indicates intent to work on fixing the issue.
When bugs are being worked on, they should be moved across into the "In progress" column. PRs for the bugs should also be added to the project, and should sit in the "in progress" column until they are approved. On approval, but pending merge they should sit in the "PR approved column". Merged and completed issues and PRs sit in the "done" column.
Feature requests follow a similar flow to bugs, except feature requests need to go through an approval cycle too. Feature requests should be added to the Feature requests project.
New feature requests go into the triage column. The project leads will then evaluate the feature request, and determine if it is a feature we are willing to implement, support, and maintain. Feature requests needing more discussion will sit in the "In review/discussion" column, and feature requests which are approved for implementation will sit in the "Approved / Ready to implement" column.
Developers should only pick up feature requests from the "Approved / Ready to implement" column, or risk a feature being rejected after working on the request.
Assignee on the Triage and review columns indicates the review process. Assignee on the approved column indicates intent to implement.
Technical debt and maintenance tasks should be added to the Maintenance and tech debt project.
This uses a simplified workflow similar to the bugs workflow. Requests should be better defined in the "Work defined" column, and should have a defined completion criteria.
Labels are used for further categorising issues as requiring specific configurations, or having a specific difficulty.
Labels are also used for a basic level of prioritisation.