Defect Management

Attachments

Attachments provide the visual and contextual evidence that developers need to understand, reproduce, and fix a defect. A well-documented defect with clear screenshots or log files can reduce resolution time significantly by eliminating back-and-forth communication.

How to Add Attachments

Open the defect by clicking it in the defects list.
Switch to the Attachments tab. A defect has two tabs, Details and Attachments.
Drop files onto the dashed Drop file here or click to browse area, or click it to open your file picker — there is no Upload button. You can select several files at once.
Each file is uploaded and appears in the attachment list. A toast reports how many succeeded and how many failed.

You can also attach files while creating the defect, from the Attachments area of the New Defect form.

Supported File Types

Category	Supported Formats	Common Use Cases
Images	PNG, JPG, JPEG, GIF, SVG, WebP, BMP, TIFF, ICO, AVIF, HEIC, HEIF	Screenshots of the UI, error messages, visual regressions
Documents	PDF, DOC, DOCX, TXT, Markdown	Specification excerpts, requirement documents, plain-text log extracts
Spreadsheets	CSV, XLS, XLSX	Test data sets, comparison tables, exported logs
Videos	MP4, MOV, AVI, MKV, WebM	Screen recordings of the defect reproduction steps

File types not in this list -- including RTF, PPTX, ZIP, RAR, JSON and XML -- are rejected on upload. To attach an application log or an API payload, save it with a .txt or .md extension.

File Size Limits

Individual files can be up to 50 MB each. Total attachment storage counts toward your organization's plan storage cap.

Attachment Best Practices

Always attach a screenshot for UI-related defects. A picture is worth a thousand words -- annotated screenshots with arrows or highlights pointing to the issue are even better.
Include relevant log files for backend or API defects. Copy the relevant error stack trace or attach the full log file so developers can locate the issue quickly.
Use screen recordings for defects that are timing-dependent or involve a sequence of user interactions that are hard to describe in text.
Name files descriptively. Instead of "screenshot.png", use something like "checkout-discount-double-applied.png" so the context is clear even without opening the file.
Trim large files. Archives are not accepted, so attach the relevant excerpt of a log as a .txt file rather than the whole thing, and crop screenshots to show only the relevant portion of the screen.

The attachment list shows the file name, size and upload date — there are no inline image previews, and the uploader's name is not shown. Every row carries a View icon, which opens the file in a new browser tab (which is how you look at a screenshot without downloading it), a Download icon, and a delete icon.

Search & Filter

As your project accumulates defects over time, the ability to quickly find specific defects becomes essential. TestKase provides keyword search and multi-criteria filtering on the defects list view to help you locate defects efficiently.

Keyword Search

The search bar at the top of the defects list allows you to search by defect title. Type any keyword or phrase and the list will filter in real time to show only matching defects. Search is case-insensitive and matches partial words.

Filtering Options

Click the filter icon next to the search bar to open the filter panel. Every filter below combines with the others and with the keyword search:

Filter	Description	Example Use
Priority	Filter by priority level to focus on the most impactful issues first. Multi-select.	Show Blocker and Critical defects during a release readiness review.
Status	Filter defects by their current lifecycle status (open, assigned, in testing, deployed, closed, achieve). Multi-select.	Show only open defects to see the current backlog that needs triage.
Assignee	Filter by the team member assigned to the defect. Multi-select.	View all defects assigned to a specific developer to assess their workload.
Created By	Filter by who reported the defect. Multi-select.	Review everything a particular tester logged during a cycle.
Updated By	Filter by who last changed the defect. Multi-select.	Find the defects a developer has just moved to in testing.
Testcases	Choose Linked or Not Linked, or type specific test case IDs to match. IDs are validated as you enter them.	Find defects that were never traced back to a test case.
Requirements	Choose Linked or Not Linked, or type specific requirement IDs.	Pull every defect reaching a particular requirement before a sign-off meeting.
Created Date Range / Updated Date Range	Two independent start/end date ranges.	Limit the list to defects raised during the current sprint.

The Assignee, Created By and Updated By filters only appear once the project has members to choose from. The Linked / Not Linked choice and the specific-ID box are mutually exclusive — picking Not Linked disables the ID box.

Common Search Scenarios

Release readiness check: Filter by Status = Open and Priority = Blocker or Critical to see all high-severity defects that could block a release.
Developer workload: Filter by Assignee to see all defects assigned to a specific team member and understand their current workload.
Verification queue: Filter by Status = Closed to find defects that are awaiting re-testing and verification. These defects have fixes applied but need a tester to confirm them.
Triage meeting preparation: Filter by Status = Open to view the full defect backlog that needs to be assigned and prioritized during the next triage session.
Area-specific investigation: Use keyword search to find all defects related to a specific feature (e.g., "checkout", "authentication", "reporting").

Combine keyword search with status or priority filters for more precise results. For example, search for "checkout" with Status = Open to see all unresolved checkout-related defects at a glance.

Clone & Export

Cloning a Defect

Select exactly one defect in the list and click Clone in the toolbar. TestKase creates a new defect with a new DEF- ID, copying the original's title, summary, priority, status and assignee. You become its Created By and Updated By.

The clone carries the record's own fields and nothing else: attachments are not copied, and neither are the links to test cases or requirements. Re-add those on the new defect if you need them.

The button is disabled unless exactly one row is selected, so it cannot be used on a multi-row or Select All selection. Guests cannot clone.

Exporting the Defect List to CSV

Click Export CSV in the toolbar to download the defect list as a CSV file.

The export respects your current filters and keyword search — what you see is what you get.
It also respects the columns you have chosen to show, including the linked test case and requirement ID columns, which the on-screen list does not always render.
If you have rows selected, only those rows are exported. With nothing selected, every row matching the current filters is exported, not just the current page.

Export is a read operation and is available to every role that can see the defect list.

Defect Reports

TestKase includes several reports specifically designed to help you analyze defect trends and distributions. These reports are available in the Reports & Analytics section of your project and provide visual breakdowns of your defect data.

Available Defect Reports

Report	Chart Type	Description	Best For
Defects by Folder	Donut	Shows how defects are distributed across test case folders in your project.	Identifying which areas of your application have the highest defect density.
Defects by Cycle	Donut	Defect counts per test cycle. Compares defect rates across different test runs.	Understanding whether defect rates are increasing or decreasing across cycles.
Defects by Tester	Donut	Defects found per tester. Shows who is discovering the most defects.	Recognizing top bug-finders and balancing workload during triage sessions.

Using Defect Reports Effectively

Sprint retrospectives: Use the Defects by Cycle report to see how many defects were found in the current sprint compared to previous sprints. An upward trend may indicate code quality issues or increased scope that needs attention.
Risk assessment: Use the Defects by Folder report to identify which modules or features have the highest defect density. These areas may need additional test coverage, code review attention, or architectural improvements.
Team insights: Use the Defects by Tester report to understand testing effectiveness across your team. Testers who consistently find more defects in critical areas are valuable assets for high-risk testing assignments.
Trend monitoring: Review defect reports at the end of each sprint or release cycle to track whether your defect rate is trending up or down over time. A decreasing trend indicates improving code quality.

For a complete overview of all available reports, including execution analytics, coverage and traceability, trend analysis, and advanced insights, see the Reports & Analytics documentation.

Defect Management

On this page