Task for a defect

Task - a technical task created to fix an identified defect.

The user creates the necessary number of tasks to fix a proposed defect. Sequentially completing these tasks will resolve and close the defect.

Planning and assigning executor and reviewer algorithm

User Actions:

Any actions are possible only if the defect for which the task was created is in the "Proposed" status.

• Creating a task (title, description, time estimate for completion, determining the required competency - skills and skill level) at any time.
• Editing task data:
• Title, description - at any time.
• Required competency:

✅ The task has not yet been on the "DOING" and "REVIEW" stages.

✅ The task is in the "TO DO" stage, and the executor has not been assigned yet.

❌ Changing competency is impossible for a task in the "DOING" stage or has already passed these stages.

❌ Changing competency is impossible for a task in the "REVIEW" stages or has already passed these stages.

❌ Changing competency is impossible for a task in the "DONE" stage.

• Time estimate for completion:

✅ The task is in the "TO DO," "DOING," or "REVIEW" stages.

❌ Changing the time estimate for completion is impossible for a task in the "DONE" stage.

• Creating/changing dependencies between tasks at any time.
• Changing the association with the Iteration at any time (tasks are moved according to the rules of task movement between Iterations).

If Iteration is defined, the task moves to the execution stage (if Iteration is defined, the task immediately goes to the stage; if Iteration is not defined, it waits for Iteration status determination). The user's choice in the Iteration field as "empty" removes the task from planning.

• Task Deletion:

✅Does not have any input/output dependencies.

✅ The task does not have an assigned executor

• Entering/Exiting Task Dependencies:

A task can be linked to other tasks with input/output dependencies (sequence of execution) or be an autonomous element related to the defect. When creating an input dependency, the system blocks the task.

On the task card for which an input dependency is created, meaning it can only be executed after the completion of work on the predecessor technical task, a symbol appears in the "Blocked" field  
, informing the user that the system is blocking the execution of this task for the performer. Once the predecessor technical task is completed (workflow stage DONE), meaning it has passed all stages of the workflow process, from assignment by the system to execution and quality review by the reviewer, this technical task will be unblocked, as indicated by the symbol  in the "Blocked" field.