...
| # | Status | Transitions (Next steps) |
|---|---|---|
| 1 |
The issue is open and ready for the assignee to start work on it. |
|
| 2 |
This issue is being actively worked on at the moment by the assignee. |
|
| 3 |
Issue is fixed in the local machine of the developer and is ready to be deployed. |
|
| 4 |
The issue is being verified by the eVision QA specialist. | Theses buttons are only available for eVision.
|
| 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. |
|
| 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. |
|
| 6 |
The issue has been deployed in the PROD environment. The client needs to close the issue if it is resolved after testing. |
|
| 7 |
A resolution has been taken, and it is awaiting verification by reporter. From here issues are either reopened, or are closed. |
|
| 8 |
This issue was once resolved, but the resolution was deemed incorrect. From here issues are either marked assigned or resolved. |
|
| 9 |
The issue is considered finished, the resolution is correct. Issues which are closed can be reopened. |  >> Reopened |
...