Monitor Issue Trends | Testlio Help Center

The status indicators in the Issues report provide a clear view of where issues stand in the resolution process. By tracking the flow of issues through various statuses, you can ensure that critical problems are being addressed efficiently, priorities are aligned, and the overall process is staying on track.

Charts in the Testlio platform showing issues across various statuses in many indicators.

Indicator	What It Tracks	What Signals It Might Bring
Open Issues	The total number of issues that were created during the period and are still open today. Automatically compares with how many issues were created during the prior period.	This metric helps you track changes in open issue volume over time. Many open issues indicates an unresolved backlog; prioritize addressing critical and high-severity issues to reduce the number. You should also review Work As Designed and Expected behaviors to ensure alignment. Decreasing open issues suggests progress; ensure the focus remains on resolving impactful issues efficiently. It’s recommended to review the scope to identify other high-priority areas.
Open Issues by Age	The number of open issues categorized by how long they’ve been unresolved (0–30, 31–60, 61–90, or 90+ days) across severity levels (high, medium, low).	This metric helps identify long-standing issues that may need prioritized attention. Many long-standing issues (90+ days) highlights potential blockers or deprioritized issues. Review with the team to ensure correct prioritization and relevance. Having mostly recent issues (0–30 days) suggests proactive issue handling. Maintain your momentum to prevent backlog growth. It’s recommended to review the scope to identify other areas to review – a good signal for automation in these areas.
Refused Issues	The number of issues refused by Testlio in the period. Automatically compares with how many issues were refused during the prior period.	An increasing number of refusals may signal misalignment on issue criteria. Refine your issue reporting processes or recalibrate the testing focus. It’s recommended to review tests and updating as needed. A decreasing number of refusals indicates improved alignment with expectations. Continue refining workflows for consistent issue approval.
Closed Issues	The total number of issues resolved within the period. Automatically compares with how many issues were closed during the prior period.	Many closed issues shows strong resolution progress. Focus on the signal of efficiency. Few closed issues suggests potential delays. Identify blockers in the resolution process and streamline workflows. Review the addressed issue process with the team.
Breakdown by Status	The percentage of issues in each status. Potential statuses: Identified: A new issue not yet approved or closed. Refused: A closed issue that was not approved by Testlio. Approved: An issue approved by Testlio. Rejected: An issue approved by Testlio but closed as rejected by the client. Addressed: An issue approved by Testlio and closed as addressed by the client.	This breakdown provides insight into the flow of issues through different stages of the resolution process. Many refused issues signals potential misalignment on issue criteria or over-reporting of non-critical issues. It’s recommended to review tests to ensure they align with feature needs. Many approved issues indicates strong alignment with expectations and testing effectiveness. Many rejected issues may reflect challenges in prioritization or acceptance criteria for the client. It’s recommended to review the scope and feature behaviors. Many rejected issues demonstrates successful issue resolution and client alignment, indicating a well-functioning process. An imbalance among statuses suggests inefficiencies or bottlenecks in issue handling, such as delays in approval or resolution stages. It’s recommended to review the process for addressed issues.
Refusal Rate	The percentage of issues refused by Testlio. Automatically compares with what percentage of issues were refused during the prior period.	A high refusal rate suggests misaligned reporting. Collaborate to refine the criteria for approval. A signal that it’s a good time to review scope expectations for these features. A low refusal rate indicates strong alignment. Focus on maintaining consistent reporting quality.
Issues by Status	A visual representation of issues over time categorized by status.	This chart helps track the volume and resolution progress of issues week by week, providing a clear view of issue handling trends. An increasing trend for open statuses indicates a growing backlog. Prioritize resolutions based on severity and client impact. It may be a good time to look at testing processes and see if the current process is supporting developer capacity and turnaround time. An stable or decreasing trend for open statuses suggests effective issue handling. Analyze trends to replicate success in future cycles.

Monitor Issues and Severity Levels

Gain Insights from the Issues Report

Track Issues

Get Approval Insights

Understand Issue Workload