Issue statuses » History » Version 1
Michele Di Maria, 09/29/2017 08:59 AM
| 1 | 1 | Michele Di Maria | h1. Issue Statuses |
|---|---|---|---|
| 2 | |||
| 3 | The statuses of the issues are intended as follows: |
||
| 4 | |||
| 5 | *NEW* |
||
| 6 | The issue has already been created and is awaiting to be followed by the Assignee. |
||
| 7 | |||
| 8 | *IN PROGRESS* |
||
| 9 | The work is in progress for the issue. It can be the Task is in being fulfilled, the Feature is being developed, the Bug is in debug, the Support request is under investigation. |
||
| 10 | |||
| 11 | *FEEDBACK* |
||
| 12 | The issue has been resolved by the original Assignee and now a feedback about the resolution has been requested to the Author or someone that can confirm the resolution has been successfully applied. |
||
| 13 | |||
| 14 | *RESOLVED* |
||
| 15 | The issue, task, feature or bug has been successfully resolved. Generally, this follows the feedback phase when the issue has been confirmed to be closed. |
||
| 16 | This status closes the issue. |
||
| 17 | |||
| 18 | *CLOSED* |
||
| 19 | The issue, task, feature or bug has been closed. Generally this means there was not a solution. In the issue notes there should be a reason why the issue has been closed and not resolved. |
||
| 20 | This status closes the issue. |
||
| 21 | |||
| 22 | *REJECTED* |
||
| 23 | The issue, task, feature or bug has not been accepted. Probably the issue is a duplicate or cannot be taken in charge. In the issue notes there should be a reason why the issue has been rejected. |
||
| 24 | This status closes the issue. |
