Issue for the executor

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 staxtus by default.
• Fixed - corrected. Accepted by the reviewer.

Possibilities and limitations for the executor during the "Doing" stage upon return:

✅ Edit the title and description of the corresponding subtask, but editing the title and description by the executor does not change the corresponding data in the Issue.

✅ Mark the subtask (Issue) as completed.

✅ Leave a comment.

❌ Create a new Issue.

❌ Change the status of the Issue.

❌ Delete an Issue and its associated subtask.

Actions of the executor:

• Task execution:
• Receive a task for revision with an identified Issue.
• Start working.

1. Review the Issue details on the "Issues" screen if necessary.
2. Mark the subtask as completed
3. Finish working on the task.