A reviewer may discover errors in the completed task during the quality assurance stage. They are registered in the system as separate entities and have rules and limitations for their successful correction by the executor.
An Issue is a defect or an error in implementation or an inconsistency between the actual result and the expected result.
When submitting a task requiring further work, an Issue created by the reviewer during the Review stage becomes a subtask for the executor.
Lifecycle:
- Proposed - suggested. When an Issue is created, it receives this status by default.
- Fixed - corrected. Accepted by the reviewer.
Possibilities and limitations for the reviewer during the "Review" stage:
✅ Create an Issue. When the task is sent for revision, each created Issue becomes a subtask for the performer.
✅ Edit the title and description of the Issue. This changes the data of the corresponding subtask for the performer.
✅ Change the status of the Issue.
✅ Leave a comment.
❌ Cannot accept the task (cannot move the task to the next workflow stage) while there are Issues in the "Proposed" status.
- An Issue in the "Fixed" status does not affect returning the task for revision for other reasons.
Actions of the reviewer:
1. Creating an Issue:
- Create an Issue.
2. Enter the necessary information:
2.1 Title
2.2 Description
2.3 Comment
3. Return to the Inbox screen
4. Return the task for revision
- The reviewer cannot move the task to the next workflow stage when there are issues in the "Proposed" status.
- Re-review of a task with a created Issue:
- Go to the "Issues" screen.
2. Return to the Inbox screen and send the task for revision.
- Task acceptance - Issue fixed:
The reviewer accepts the task and changes the Issue status to "Fixed."
- An Issue in the "Fixed" status does not affect returning the task for revision for other reasons.
Comments
0 comments
Article is closed for comments.