The defect detail page is where you update a defect as it moves through its lifecycle — reassigning it, changing its status, linking test cases, and recording notes. You can also delete the defect or convert it into a user story directly from this page.
You can open a defect from two places:
All fields on the defect detail page can be updated at any time. Changes are saved immediately when you make them.
| Field | Notes |
|---|---|
| Title | Click the title to edit it inline. Update it to be more specific as more information becomes available. |
| Status | Move the defect through its lifecycle: Open → In Progress → Fixed → Verified → Closed. Can also be set to Rejected or Converted to Story. |
| Developer | The team member responsible for fixing the defect. Update when reassigning. |
| QA | The QA member who will verify the fix. Assign before the fix is ready for verification. |
| Severity | Impact level: Critical, High, Medium, or Low. Update if the actual impact turns out to be different from the initial assessment. |
| Reproduction & Behavior | Steps to reproduce the defect from a known starting state. Update as the reproduction path becomes clearer. |
| Expected Behavior | What should happen when the steps are followed — the correct, intended behaviour. |
| Root Cause & Resolution | Filled in by the developer once the cause is identified. Describes what was wrong and what fix was applied. Valuable for future reference and post-mortems. |
| Verification Proof | Evidence that the fix works — screenshots, test results, or a short description of how QA confirmed the fix. Filled in during the verification step. |
| Test Cases | Link one or more test cases to this defect. Select from existing test cases in the project. Helps trace which test coverage the defect affects. |
The right side of the defect detail page has two tabs for discussion and audit information.
| Tab | What it contains |
|---|---|
| Remarks | A shared notes area for the defect. Use it to add context, decisions, workarounds, or any information that does not fit in the structured fields. All project members with access can read and add remarks. |
| History | Full audit trail of every change made to this defect — field updates, status transitions, assignments, and remarks — with timestamps and the name of the user who made each change. |
To delete the defect, click the Delete Defect option on the detail page. You will be asked to confirm before the defect is permanently removed. Deletion cannot be undone — if you are unsure, consider setting the status to Rejected instead.
If a defect represents work that should be planned and estimated as a user story, use the Convert to Story option on the detail page. This creates a new story pre-filled with the defect's title and description, and updates the defect's status to Converted to Story. The original defect remains in the Defect List for traceability.
I can't edit any fields on the defect
Editing requires contributor access or above. Read-only members can view defects but not update them. Ask your project manager to update your access level.
The "Convert to Story" option is not available
Convert to Story requires project manager or contributor access. If the option is missing, check your role with the project manager.
I converted the defect to a story by mistake
The conversion cannot be automatically undone. The created story can be deleted from the Story List, and the defect status can be manually updated back to its previous state.
The "Delete Defect" option is missing
Deleting a defect requires contributor access or above. If the option is not visible, check your access level.
The Test Cases field is empty — no options to select
Test cases must be created in the project before they can be linked to a defect. Go to the Test Cases section to create them first.
My status change is not saving
Some status transitions may require fields like Developer or QA to be filled first. Check if there is a validation message and fill in the required fields before changing the status.