Overview
The Defect Management page has two tabs:Dashboard
The Dashboard gives you a real-time snapshot of your defect landscape.Status counters
Six cards at the top show a count for each status:Charts
- Status Overview — Donut chart showing distribution of defects across all statuses
- Priority Breakdown — Bar chart showing defect count by priority (Low, Medium, High)
- Severity Breakdown — Bar chart showing defect count by severity (Major, Critical, High)
- Team Workload — Progress bars showing the percentage of defects assigned to each team member
Filtering by date
Use the Select Range dropdown to filter all dashboard data:- Last 7 days
- Last 30 days
- Last 90 days
- Last 6 months
- Custom date range
Defect Board
The Defect Board is a Kanban view with a column for each status. Defects appear as cards that can be moved between columns.Moving defects between statuses
Drag and drop any card to a different column to update its status. The change is saved automatically.Defect cards
Each card shows:- Title of the defect
- Severity badge — colour coded:
- Green = Minor
- Yellow = Major
- Red = Critical
- Priority badge — colour coded:
- Blue = Low
- Orange = Medium
- Red = High
- Defect ID (e.g. DEF-AHP-007)
- Assignee initials avatar
- Reopened badge (if the defect has been reopened)
Card actions
Click the ⋯ menu on any card to:- View — see full defect details, attachments, and linked test case
- Edit — update any field on the defect
- Delete — permanently remove the defect (requires confirmation)
Creating a defect
Click Create Defect on the Defect Board. You can also create a defect directly from a failed test case during manual execution — click the Create Defect button that appears when you mark a test case as Failed.Defect form fields
text
required
A clear, concise description of the defect. Minimum 2 characters.
select
required
The current state of the defect. Defaults to New on creation.
select
required
How severe the impact is:
- Critical — system is unusable or data is at risk
- Major — significant feature is broken
- Minor — minor issue with a workaround available
select
required
How urgently it needs to be fixed:
- High — must be fixed immediately
- Medium — fix in current sprint
- Low — fix when time allows
text
required
Where the defect was found. Example:
Staging, Production, localhosttext
required
Detailed steps for the developer to reproduce the issue. Be as specific as possible.
select
Optional. Assign the defect to a team member.
select
Optional. Select the module this defect belongs to. Used to filter the test case list.
multiselect
Optional. Link one or more published test cases to this defect. Select a module first to filter the available test cases.
file
Optional. Upload screenshots, recordings, or other evidence. Supports JPG, PNG, MP4, WEBM — max 5 files, 100MB each.
Defect lifecycle
A defect typically moves through the following workflow:Generating a defect report
Click Defect Report on the Defect Board to download a PDF report. The report includes:- Defect Overview — total logged, open, closed, reopened, and reopen rate
- Defects by Status — table with counts for each status
- Defects by Severity — table with severity breakdown
- Defects by Module — table showing defect counts per feature area
- Trend Chart — line graph showing open vs closed defects over time
- Top 5 Open Critical Defects — table with ID, title, assignee, status, and reported date
Filtering and searching
- Search — type in the search box on the Defect Board to filter cards by title
- Date Range — filter defects on both the Dashboard and Defect Board by a preset or custom date range
Permissions
What’s next?
Running Tests
Log defects directly from failed test cases during execution
Inviting Users
Add team members to assign defects to