Accessing the Report
Navigate to More Reports > Full Resolution Time for Bugs from the left sidebar. This report requires an active Jira integration.
The subtitle reads: "Improve customer satisfaction by resolving bugs faster."
The top-right corner has two buttons:
Export — download the report data
Configure — adjust how Full Resolution Time is calculated (see Configuration below)
Filters
Filter | Options |
Date range | Preset ranges (Last 3 Months, etc.) or custom dates |
Team selector | My Teams, All Teams, or specific teams |
Apply Filter | Additional filters (repositories, members) |
Save Filters | Save your current filter combination |
A "Showing all Repositories" badge appears when no repo filter is applied.
Tabs
The report has two tabs:
Tab | What it shows |
Full Resolution Time | How long bugs take to resolve (the primary view) |
# of Bugs | Bug volume over time |
Full Resolution Time Tab
Headline Metric
At the top of the tab, you see:
Full Resolution Time for Bugs — described as "Time it takes to resolve a bug when it is raised with an engineering team"
A headline number (e.g., 13 days / bug) with a trend arrow
Green down arrow = resolution time is decreasing (improving)
Red up arrow = resolution time is increasing (worsening)
Trend Chart
A time-series chart showing Full Resolution Time over the selected period, with gray data points and a blue trend line.
By Priority
A bar chart showing Full Resolution Time broken down by Jira bug priority (e.g., Highest, High, Medium). This reveals whether high-priority bugs are being resolved faster than lower-priority ones.
What to look for:
Highest/High priority bugs should have the shortest resolution times
If High priority takes longer than Medium, your prioritization process may not be working
By Team
A bar chart showing Full Resolution Time for each team, with the Organization Average shown as a gray reference bar. This makes it easy to spot which teams are resolving bugs quickly and which are falling behind.
What to look for:
Teams significantly above the org average may need support or process changes
Teams well below the average may have practices worth sharing
# of Bugs Tab
Switch to this tab to see bug volume over time. This helps you understand whether the team is dealing with an increasing bug load, which can explain rising resolution times.
Configuration
Click Configure in the top-right corner to adjust how Full Resolution Time is calculated. Configuration options are available at Settings > Configure Metrics > FRT.
You can define:
Bug start event — when the clock starts (e.g., Jira issue created, Jira in progress, PR created)
Bug end event — when the clock stops (e.g., Jira done, PR merged, PR released)
The default calculates from issue creation to Done status.
How Full Resolution Time Is Calculated
Full Resolution Time = Bug End Event - Bug Start Event
This is the total elapsed calendar time. Weekends and non-working hours are included (Haystack uses 24/7 calendar time for all metrics).
The headline number uses the 85th percentile, consistent with other time-based metrics in Haystack.
Best Practices
Use the Priority breakdown to validate your triage process. If Highest-priority bugs aren't resolved fastest, the team may not be prioritizing effectively.
Use the Team breakdown to balance workload. If one team has dramatically higher resolution times, they may need more capacity or better tooling.
Track the # of Bugs tab alongside resolution time. Rising bug counts with stable resolution time means the team is keeping pace. Rising bug counts with rising resolution time means the team is falling behind.
Configure the metric to match your workflow. If bugs go through a triage queue before reaching engineering, consider starting the clock at "In Progress" rather than "Created."
FAQ
Q: Is this the same as First Response Time? A: No. Full Resolution Time measures the total time from bug creation to resolution. First Response Time (available in the Code Review Stats context) measures only the time to the first action. This report tracks the entire lifecycle.
Q: Do weekends count toward resolution time? A: Yes. All metrics in Haystack use 24/7 calendar time.
Q: Why is my resolution time so high? A: Check if old, unresolved bugs are included in the data. A few very old open bugs that recently got closed can dramatically inflate the 85th percentile. Consider filtering to a shorter date range or reviewing your backlog grooming process.
Q: Which Jira issue types are included? A: Bug issues by default. The Configure option lets you adjust which issue types and events are tracked.
Q: Who can access this report? A: Both Admin and Member roles. The data shown depends on the team filter selected.