Defects are part of the process. There are defects discovered during the quality check of a completed technical task—before the task is considered finished—and those found either during or after the implementation of an Objective.
- During the quality control stage, defects in the implementation of technical tasks may be identified. In such cases, the task is returned to the executor for correction.
- Defects found during or after the implementation of an Objective: we log the problem, investigate what went wrong, and determine who will fix it—either by returning the task to the responsible person or identifying someone with the required expertise to resolve it.
Lifecycle:
Proposed - suggested. By default, a defect receives this status when created.
Fixed - resolved.
The user creates the necessary number of tasks to fix a proposed defect. Completing the tasks sequentially resolves and closes the existing defect.
User Actions:
- Defect Creation (title, description, status) at any time
- Editing defect data: Title and description - at any time
- Creating new tasks to fix defects and define their properties
- Determining dependencies between tasks
- Defect statuses
- Relationship between Defect and Objectives
- Priority of the executor for fixing the defect
Comments
0 comments
Article is closed for comments.