Bug for the reviewer

During the quality assurance stage, a reviewer may discover errors in the completed task. They are registered in the system as separate entities and have rules and limitations for their successful correction by the executor.

A bug is a defect or an error in implementation, or an inconsistency between the actual result and the expected result.

A bug created by the reviewer during the Review stage when submitting a task that requires further work becomes a subtask for the executor.

Lifecycle:

• Proposed - suggested. When a bug is created, it receives this status by default.
• Rejected - declined. If a bug is proposed by a reviewer, sent back for re-review, but not fixed, it is moved to the rejection status to be returned to the performer. The completion of the subtask created to fix this bug is canceled.
• Fixed - corrected. Accepted by the reviewer.

Possibilities and limitations for the reviewer during the "Review" stage:

✅ Create a bug. Each created bug, when the task is sent for revision, becomes a subtask for the performer.

✅ Edit the title and description of the bug. This changes the data of the corresponding subtask for the performer.

✅ Change the status of the bug.

✅ Leave a comment.

❌ Cannot accept the task (cannot move the task to the next workflow stage) while there are bugs in the "Proposed" or "Rejected" status.

• A bug in the "Rejected" status cancels a completed subtask if the task is returned for revision for the second time (unchecking the checkbox for the performer).
• A bug in the "Fixed" status does not affect returning the task for revision for other reasons.

Actions of the reviewer:

• Creating a bug:
• Create a bug.

 
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 while there are bugs in the "Proposed" or "Rejected" status.

• Re-review of a task with a created bug:
• Go to the "Bugs" screen.

 
2. If necessary, repeat the step of "Creating a new bug" if a new bug has appeared. Or, if the bug is not fixed, change the bug status to "Rejected" to return the task to the executor.

 

• A bug in the "Rejected" status cancels a completed subtask if the task is returned for revision for the second time (unchecking the checkbox for the performer).

3. Return to the Inbox screen and send the task for revision.

• Task acceptance - bug fixed:

The reviewer accepts the task - changes the bug status to "Fixed."

 

• A bug in the "Fixed" status does not affect returning the task for revision for other reasons.