Status
* All actions sent email to subscribers (participants on an issue).
Statuses
# | Status | Transitions (Next steps) | |
---|---|---|---|
1 | The issue is open and ready for the assignee to start work on it. | >> In Progress >> Open Transition screen >> Closed | |
2 | This issue is being actively worked on at the moment by the assignee. | >> Fixed Locally >> Open Transition screen >> Resolved in TEST >> Open Transition screen >> Resolved in PROD >> Open | |
3 | Issue is fixed in the local machine of the developer and is ready to be deployed. | >> Open Transition screen >> Resolved in TEST >> Open Transition screen >> Reopened | |
4 | |||
Issue was deployed in the TEST environment (or PRE-PROD/STAGING environnement if the client has their own environnement for QA). The client needs to transition the issue if it is confirmed to work after testing. | >> Open Transition screen >> Push to PROD >> Open Transition screen >> Reopened >> Open Transition screen >> Closed | ||
5 | Issue has been validated by the client in the TEST environment (or PRE-PROD/STAGING environnement) and is ready to be pushed to PROD environment. | >> Open Transition screen >> Resolved in PROD >> Open Transition screen >> Reopened | |
6 | The issue has been deployed in the PROD environment. The client needs to close the issue if it is resolved after testing. | >> Open Transition screen >> Reopened >> Open Transition screen >> Closed | |
7 | This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved. | >> In Progress >> Closed | |
8 | The issue is considered finished, the resolution is correct. Issues which are closed can be reopened. | >> Reopened |
...
Transitions Screens
# | Screen | Description | ||||||
---|---|---|---|---|---|---|---|---|
1 |
|
| ||||||
2 |
|
| ||||||
3 |
| |||||||
4 | ||||||||
|
| |||||||
4 |
|
|