If you’re using Jira dashboards to understand how your team is performing — that’s great. You already know that visibility matters. But here’s the real question: are you measuring activity or time?
Because when it comes to workflow performance, time is what determines everything.
You can see how many issues are in QA or how many have moved to “Done.” You can even track how many times an issue has changed statuses. But without a Jira average time in status gadget, you can’t truly see where issues are getting stuck or identify the bottlenecks slowing your workflow.
Jira provides built-in dashboard gadgets, such as Average Time in Status and Average Number of Times in Status, which provide helpful insights into workflow behavior. At the same time, many organizations need deeper visibility into cycle time, SLA performance, and overall workflow predictability.
In this guide, we’ll explore why it is important to track average time in status, whether Jira can calculate it natively, and how adding a dedicated gadget can significantly enhance your Jira dashboard reporting and performance visibility.
Let’s dive in.
Table of contents:
- What is a Jira Dashboard Gadget?
- What Are Built-In Jira Time in Status Gadgets?
- When Do Teams Need More Advanced Time in Status Analytics?
- Time in Status by SaaSJet – Advanced Jira Average Time in Status Gadget
- How to Get Started with the Time in Status Gadget
- New to Time in Status?
- FAQ
What is a Jira Dashboard Gadget?
A Jira dashboard gadget is a customizable widget that visualizes specific data on a Jira dashboard. Gadgets help teams visualize project metrics, issue statistics, sprint progress, and workflow insights in one centralized view. Instead of jumping between filters and reports, users can configure Jira dashboard gadgets to surface the information that matters most — in real time and in a single place.
Jira comes with several built-in dashboard gadgets, including filter results, pie charts, sprint health reports, and average time in status reports. These tools give teams quick visibility into activity and workflow patterns. By combining multiple Jira dashboard gadgets, organizations can build role-specific dashboards tailored to engineering managers, project managers, support teams, and executives.
What Are Built-In Jira Time in Status Gadgets?
Jira includes several built-in dashboard gadgets that show how issues move through workflow statuses. The most commonly used gadgets are “Average Time in Status” and “Average Times in Status.” These built-in Jira average time in status gadgets help teams understand workflow behavior directly from the dashboard.
The “Average Time in Status” gadget shows the average time that resolved issues spent in each workflow status. It gives teams a general idea of how long work typically stays in stages such as “In Progress,” “QA,” or “Done.” This gadget is especially useful for analyzing past results and identifying general trends in completed work.
The “Average Number of Times in Status” gadget counts how many times issues have entered a given status. Instead of focusing on time, it highlights workflow patterns, such as issues constantly moving between development and quality assurance, which could be a sign of rework or process instability.
These two Jira “Time in Status” gadgets give a basic workflow analysis. They assist teams in monitoring activities, analyzing historical data, and acquiring a basic understanding of issue workflow.
When Do Teams Need More Advanced Time in Status Analysis?
The average time in status gadgets in Jira are very effective for teams that require a high degree of transparency. However, as the complexity of work processes increases, many teams find that they need more than just basic analysis. When you are handling multiple projects, analyzing service-level agreement commitments, comparing team performance, or analyzing active issues rather than resolved issues, you require more advanced time-based data.
More advanced status time analysis is required when cycle times vary from sprint to sprint, bottlenecks appear unevenly, or management requires trend analysis rather than snapshots. Teams that rely on accurate workflow optimization, especially in engineering, ITSM, or enterprise teams, require more advanced filtering, date-range analysis, business calendars, and real-time visibility into current work.
In such cases, the need for a more flexible average time in status gadget with advanced filtering becomes essential to accurately measure performance.
Time in Status by SaaSJet – Advanced Jira Average Time in Status Gadget
Time in Status by SaaSJet is an advanced Jira reporting tool that also serves as a powerful Jira average time in status gadget, providing teams with deeper visibility into how work moves through their workflows. It includes the main features available in Time in Status — and even more. The gadget lets you view the metrics and reports you care about without opening the plugin. Once configured, the most important numbers, charts, and statistics from the application are always visible and easily accessible right from your dashboard.
Main gadget’s features:
- All reports from the app are available: Time in Status, Assignee Time, Average Time, Status Entrance Date, Time in Status per Date, Status Count and Transition Count. You can find more detailed information about each report type in the documentation.
- With Advanced configuration options, you can customize the gadget to fit your specific needs. Set your preferred data filters, define custom date ranges, and choose the appropriate team calendar — whether you track time 24/7 or only during working hours.
- Chart and issues list view. Visualize workflow performance through clear, easy-to-read charts and get an overall picture of how work is moving across statuses. The following types of charts are available: Area, Bar, and Pie.
This combination of detailed data and visual insights helps move from raw numbers to a practical understanding of the workflow.
How to Get Started with the Time in Status Gadget
Ready to add deeper workflow visibility to your Jira dashboard? Getting started with the Time in Status Gadget is easy. Here’s what you need to do.
1. Make Sure the App Is Installed.
First, ensure that you are using the latest version of Time in Status. If you have already installed the add-on, ensure that it is updated to take advantage of all the latest improvements.
2. Add the Gadget to Your Dashboard.
- In Jira, go to Dashboards.
- Click the Add Gadget button.
- Write “Accurate time in status” in the search box.
- Select Accurate Time in Status (by SaaSJet) at the search results.
- Click Add to place it on your dashboard.
3. Configure Your Report.
After adding the gadget to your dashboard, follow these steps to configure your report:
- Open the configuration panel and choose the type of report you would like to view
- Apply filters (project, sprint, assignee, or JQL)
- Choose the date range you prefer
- Select the team calendar that suits you best
In a matter of minutes, your dashboard will display the metrics that are most important to your workflow.
New to Time in Status?
If you haven’t tried the app yet, now’s a great time to explore it.
Install Time in Status from the Atlassian Marketplace and discover its full reporting capabilities — including advanced dashboard gadgets, flexible time-based analytics, and powerful workflow insights.
Start turning your Jira dashboard into a true workflow intelligence center.
FAQ
What is the time in status gadget in Jira?
A time in status gadget in Jira is a dashboard gadget in Jira that shows the amount of time spent in each workflow status. This gadget works on the principle of issue transition history to provide statistics on the time spent between changes in issue status. It presents the data in a visual or tabular format directly on a Jira dashboard.
This allows teams to see how much time is spent in stages such as In Progress, QA, Review, or Done. By tracking time in status, teams can monitor the efficiency of their workflow, identify delays, and improve delivery predictability.
While some Jira gadgets offer some average time reporting, other advanced applications offer detailed time spent within statuses such as active issues, custom date ranges, and business calendars.
What is the difference between Time in status and Number of times in status?
The difference lies in duration vs frequency.
- Time in status measures how long an issue has been in a particular status.
- Number of times in status measures how many times an issue has entered a particular status.
For example:
- If an issue has been in the QA status for 3 days, that is Time in status.
- If an issue has entered the QA status 4 times, that is Number of times in status.
Time in status can help with bottleneck detection, whereas Number of times in status with rework detection, repeated transitions, or unstable workflows.
What is the cycle time gadget in Jira?
The cycle time gadget in Jira monitors and measures the overall time taken for an issue to be completed from the beginning of active work, such as “In Progress,” to its completion, which is “Done.” Cycle time measures how long it takes to complete an issue after development begins.
Even though Jira does not offer an out-of-the-box cycle time gadget, cycle time can be measured using Jira’s workflow data, time in status report, or the dashboard app.
Agile teams often use cycle time to monitor delivery speed and efficiency.
How can a Jira dashboard gadget help identify bottlenecks?
A dashboard gadget in Jira enables teams to identify bottlenecks in their workflow through the visualization of delays.
It becomes easier to identify bottlenecks in the workflow when the average time spent in a particular state or the current time spent in a state is shown in the gadget.
For example, if the average time spent in QA is longer compared to the average time spent in Development, then it indicates that QA is a bottleneck.
It becomes easier to:
- Identify workflow slowdowns early
- Compare sprints easily
- Identify overwhelmed team members
- Improve workflow process efficiency
- Without the dashboard gadget in Jira, it becomes harder to identify bottlenecks in the workflow since they are often invisible behind simple issue counts.
Can I track SLA using time in status?
Yes, time in status can be utilized to enable SLA tracking in Jira.
By tracking the time spent in a particular status, such as Waiting for Support, In Progress, or Pending Approval, teams can monitor their responses and resolution against a particular service level agreement.
For more accurate tracking of service level agreements, teams can make use of:
- Business calendars (working hours vs. 24/7 tracking)
- Custom date ranges
- Real-time reporting of active issues
Time in status is the foundation of time-related information needed to monitor service level agreements.
