-
Notifications
You must be signed in to change notification settings - Fork 41
Issue Workflow
This document formally documents the workflow of using the GitHub issue tracker for handling Specify 7 bugs and feature requests.
New issues should be entered into the tracker and assigned a type: label (type:bug and type:enhance are the most common).
Additionally, every issue must be assigned to one or multiple Projects.
Newly assigned issues automatically appear in the Unsorted column of the project board.
Once a bug is reproduced or the enhancement is reviewed and approved as a priority, it is moved from the Unsorted into To Do column in each project it belongs to.
While the issue is in the process of being fixed, it is moved from the To Do to the In progress column.
It is recommended that each issue is fixed on a separate branch and that a draft pull request is opened for each issue that reaches this stage (don't forget to link the pull request to an issue).
In some cases, multiple issues can be linked to single pull requests.
After the issue is fixed, it is moved from the In progress to Ready on branch column.
The draft pull request is converted into a regular pull request.
Pull requests must be assigned to at least one member from the Dev Testing and UX Testing team, if applicable (it depends on the nature of the code changes).
Dev Testing team is responsible for code review, while UX Testing verifies the behavior of the feature.
After Dev Testing team and UX Testing team approved the issue and automated tests completed successfully, the issue is merged into the next-release branch.
next-release branch should undergo general testing once a month, at which point it gets merged into production.