Track Issues | Testlio Help Center

The overview indicators in the Issues Report guide you on how well your issue processes and resolution are performing over time. Knowing how to unlock these indicators helps you stay up-to-date on processes, balance priorities, and confidently drive improvements.

The Issues report in the Testlio platform with an overview with key indicators.

Indicator	What It Tracks	What Signals It Might Bring
Identified Issues	The total number of new issues identified within the period, including those not approved by Testlio. Automatically compares with how many new issues were identified during the prior period, showing changes in issue identification rates.	A significant increase in issues could signal regression or new feature instability. A decrease indicates stability in the current scope of testing. It’s recommended to review the scope and see if there is more to add to the scope or process of testing.
Issues per Hour	The average rate of issues identified per manual testing hour during the period.	This metric provides insight into the frequency of issue discovery across the app testing process. A high rate indicates effective discovery of issues from new features, but could also highlight environment instability – it's recommended to dive into the root cause. A low rate may suggest stability in the current scope of testing – it's recommend to revisit the scope.
Issues per Run	The average number of issues identified per test run.	This metric helps identify the efficiency of each run by showing how many problems are surfaced in each execution. This allows the team to dig in to see if an increase in issues is due to a specific release, feature, or environmental area. A constant low rate of issues per run signals that it’s time to revisit the testing strategy and scope.
Issues per Hour	A visual representation of the rate of issue identification over time.	This chart gives you a deeper dive into the issues per hour signal, providing insight into quality levels and stability. Seeing spikes of high rates shows when they occurred and which runs caused them to help the team change priorities and update the testing scope. A long period of a low issue rate signals it may be time to revamp strategy to other areas.

Issue Severity Review

Go deeper into the overview by reviewing a breakdown of issues by severity, allowing you to better understand their impact.

These Indicators allow you to filter by date range or workspace, giving you a clear view of where the most critical issues are emerging. By focusing on severity, you can ensure that priorities are aligned and attention is given to the issues that matter most, keeping your testing efforts sharp and impactful.

Charts in the Testlio platform showing issue severities over time.

Indicator	What It Tracks	What Signals It Might Bring
High-Severity Issues	The total number of high-severity approved issues within the period. Automatically compares with how many high-severity issues were identified during the prior period.	This metric provides insight into the stability of high-priority functionalities. An increasing count signals instability or the need for a severity mapping review. It marks a good time to ensure the strategy on high-severity issues is up-to-date. A decreasing count suggests stability, but also a reason to review the testing strategy to see if it's desired to focus on other areas.
Breakdown by Severity	The percentages of approved issues across severity levels (high, medium, low).	This indicator helps you prioritize responses based on the impact level of each issue and assess overall quality trends within the period. Many high-severity issues means it is time to review the issue process for expectations and heat mapping. Many low-severity issues means you should look at the issues by feature map to see if there are any features causing noise.
Medium-Severity Issues	Indicates the total number of approved medium-severity issues in the period.	It is good to compare this number with the issues by feature map. By diving into which areas have the most medium-severity issues, you can manage scope and focus on your needs.
Issues by Severity vs. Testers	A visual representation of approved issues categorized by severity (high, medium, low) over time alongside the number of testers involved.	This metric helps you track the balance between issues found and tester allocation, ensuring that resources align with testing demands. The chart help the team determine if they are assigning the right amount of resources to a task. If issues stay about the same but the testers increase or decrease, you should reexamine staffing/assignments.

Issues by Run

A chart in the Testlio platform showing issues for runs over time divided by color into severity.

Indicator	What It Tracks	What Signals It Might Bring
Issues by Run	The number of approved issues per test run categorized by severity (high, medium, low). Each bar represents a single test run, with color-coded segments indicating the severity level of the issues discovered during that run.	This visualization helps track the frequency and criticality of issues across individual test executions, providing insight into both the consistency and quality of testing efforts over time. Many Issues in a run may be natural. For major releases or new feature runs, a higher count is expected and signals the need for focused follow-up testing. But ensure the issues align with expectations and critical areas. Few Issues in a run may, especially for regression runs, indicate improved stability but should prompt a review of the scope to ensure all critical areas are being tested and nothing is missed.

Issues by Feature and Severity

A chart in the Testlio platform with boxes representing features in different sizes (to represent the number of issues) and colors (to represent the average severity.

Indicator	What It Tracks	What Signals It Might Bring
Issues by Feature and Severity	A visual breakdown of approved issues by feature categorized by severity. Each block represents a feature with its size indicating the number of issues identified within that feature and its color intensity showing the severity level.	This chart helps you quickly pinpoint which features are experiencing the most critical issues. This layout aids in prioritizing efforts for issue resolution by highlighting areas with a higher volume of high-severity issues. Many high-severity issues in a feature indicates critical instability; the feature likely requires immediate attention and targeted fixes. Many medium-severity issues in a feature suggests that while not critical, these issues may impact the user experience and should be prioritized for resolution before the next major release. Many low-severity issues in a feature points to less impactful but numerous issues; consider whether these warrant immediate attention or can be deferred. An uneven distribution of issues across features may indicate that certain features are more prone to instability or are under-tested. No issues in a feature could signal stability or a gap in testing coverage, particularly for complex or high-risk areas.

Escaped Issues

Track Tests

Monitor Execution Trends

Analyze Results and Quality

Monitor Issues and Severity Levels