Defects

An error in implementation or a discrepancy between the actual and expected results.

Lifecycle:

Proposed - suggested. By default, a defect receives this status when created.

It is fixed - resolved.

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

Status Proposed

✅ Possible:

• Edit defect data.
• Delete the defect (if there are no associated tasks).
• Create a task (title, description), attach or detach attachments, determine the required competency and estimate (mandatory condition for task inclusion in planning), and specify the Product Increment (PI).

If PI is defined, the task moves to the execution stage (if PI is defined, the task immediately goes to the stage; if PI is not defined, it waits for PI status determination).

• Edit all task data and the connection with PI.

The user's choice in the PI field to be "empty" removes the task from the Kanban board.

• Delete tasks in draft status (if there is no competency and estimate or there is no connection with PI).
• Change PI (tasks are moved according to the rules of task movement between PIs).

❌ Impossible:

• Delete a task that is already in the execution stage during the workflow.
• Change competency in a task that has an assigned executor.

Status Change:

Change the defect status to "Fixed":

If there are no tasks associated with it.

Change to "Fixed" if all related tasks are in the "Done" stage.

Status Fixed:

The defect has been resolved.

Mandatory rule - all tasks must be in the "Done" stage.

❌ Impossible:

• Create new tasks.
• Make any changes to existing tasks.
• Delete the defect.
• Delete the task.

Status Change:

Transitioning a Bug to the "Proposed" status from the "Fixed" status, even when the task is already in "Done," is possible. This allows for creating new tasks related to this bug, and tasks in "Done" remain in "Done."