Viewing Defects – Details & Traceability
The Defect Details page provides a complete view of a defect, including its description, current status, assignments, external links, traceability, comments, and change history. This view is designed to help teams quickly understand the issue, its context, and its impact.
Accessing a Defect
You can open a defect from multiple places:
- Defects List – Click on any defect row
- Test Execution – Open a defect created or linked during execution
- Traceability Links – Navigate from a linked test case, execution, or release
Each defect opens in a dedicated Defect Details view.
Defect Header
At the top of the page, you’ll see:
-
Defect Code
A unique, system-generated identifier (e.g.,BUG-89) -
Title
The title of the defect. This is editable and can be changed at any time. -
Age Indicator
Shows how old the defect is (e.g.,23D OLD) to highlight stale issues
This helps you quickly understand where you are and how long the defect has been open.
Defect Tabs
Below the main details, the defect view is organized into tabs.
Details
Description
The description supports rich text formatting, including:
- Headings and lists
- Inline code blocks
- Links
- Tables
For defects created from executions, the description may be auto-generated using:
- Consolidated step descriptions up to the failing step
- Rich formatting (without media)
Users can freely edit or refine the description after creation.
Reporter
- Displays who reported the defect
- Auto-filled for execution-created defects
- Not editable after creation
Assignee
- Assign the defect to a team member
- Supports quick assignment actions (e.g., Assign me)
- Can be changed as work progresses
Status
Represents the current lifecycle state of the defect.
Examples:
- New
- In Progress
- In Test
- Verified
- Closed
- Reopened
Status changes are tracked automatically in the history.
Priority
Indicates how urgently the defect needs to be addressed.
Examples:
- Critical
- High
- Medium
- Low
Priority may be prefilled from the test case when created from execution.
Severity
Indicates the impact of the defect on the system.
Examples:
- Blocker
- Critical
- High
- Moderate
- Low
Severity helps teams assess risk independently of priority.
Due Date
- Optional
- Used for planning and tracking deadlines
- Helpful for release and sprint planning
Comments
- Used for discussion and collaboration
- Add updates, clarifications, or questions
- Supports rich text formatting
Comments are ideal for:
- Developer–QA communication
- Investigation notes
- Resolution explanations
Traceability
The Traceability tab shows how the defect connects to the rest of the system.
It may include links to:
- Test Cases
- Test Executions
- Releases
- Requirements
This helps teams:
- Understand where the defect was found
- Identify impacted areas
- Perform root-cause analysis
History
The History tab provides a full audit trail of the defect.
Tracked changes include:
- Status updates
- Priority or severity changes
- Assignment changes
- External integration updates
- Field edits
Each entry shows:
- What changed
- Who made the change
- When it happened
This ensures transparency and accountability.
Actions Menu
At the bottom of the sidebar, the Actions menu may include:
- Delete Defect (if permitted)
- Archive Defect
- Additional project-specific actions
Available actions depend on your role and permissions.
Best Practices for Reviewing Defects
- Start with Traceability to understand context
- Review auto-generated descriptions for accuracy
- Check History before making major updates
- Keep comments actionable and concise
- Update status promptly to reflect progress
Next Steps
- Learn how to Create Defects
- Explore Defect Filters & Insights
- Review Defect Best Practices