nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Is it possible to track (in hours or days) how long a ticket has spent in the different status's?

Tom Rosenberg

A ticket is 'Created' then get changed to 'Open' or 'In Progress', then gets changed to 'Waiting for Engineer', then back to 'Open' then to 'Waiting for Customer', then to 'Closed'.
I am hoping to be able to to work out the averages of the time spent in ALL the status's for groups of tickets from different 'Issue Types'.
Example: For 'Bug' tickets raised in June on average they spent:
x hours in 'New', y hours in 'Open', z hours 'waiting for engineer' and so on.......

Any guidance gratefully received..🙏

Accepted answers

All comments

Joe Pitt

there are some plugins Check out https://community.atlassian.com/t5/App-Central/Time-in-Status-in-Jira-What-is-it-and-how-to-track/ba-p/2275979

Gizem Gökçe (OBSS)

Hello @Tom Rosenberg ,

Welcome to the community!

There is no built in solution in Jira for this. So in order to track the time spent on each status I suggest you use a marketplace app. Timepiece - Time in Status for Jira ,the oldest and leading "Time in Status" app in Atlassian Marketplace, which is developed by my team at OBSS, has a report type that will meet your need. Our app is available for both Jira Cloud, and Data Center.

Timepiece mainly allows you to see how much time each issue spent on each status or each assignee.

Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. You can combine the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example average time spent on statuses per created month, issuetype, request type, etc. Please see the screenshot below that I prepared for your case.

Timepiece Screenshot.png

The app calculates its reports using already existing Jira issue histories so when you install the app, you don't need to add anything to your issue workflows and you can get reports on your past issues as well.

Timepiece reports can be accessed through its own reporting page, dashboard gadgets, and issue view screen tabs. All these options can provide both calculated data tables and charts.

Visit Timepiece - Time in Status for Jira to explore how our JIRA add-on can revolutionize your metrics measurement process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

Tom Rosenberg

Hi @Gizem Gökçe _OBSS_ thank you for that answer. I had heard of 'Time in Status', but was curious if it was possible in the regular platform. 👍🏼

Tom Rosenberg

👍🏼

Amay Purohit_RVS

Hi @Tom Rosenberg

Welcome to the community !!

You can use Jira Rest APIs to capture this information or you can use a third party app as well to get this data easily. If you are open to try out one, do take a look at

Time in Status Reports

One of the many reports which the app provides is Time in Status ie how much the issue spent in which status.

The app has 20+ reports to meet a variety of time in status use cases. Do give it a try.

More Details here

Disclaimer : I work for the vendor who built this app

Mehmet A _Bloompeak_

Hi @Tom Rosenberg

Welcome to the Atlassian Community!

There is no built-in solution for time in status info in Jira. If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Status for Each Issue report.

For further details, you can have a look at Status Time Reports How to Videos.

This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
Status durations are calculated according to the working calendar you define. Once you enter your working calendar into the app, it takes your working schedule into account too. That is, "In Progress" time of an issue opened on Friday at 5 PM and closed on Monday at 9 AM, will be a few hours rather than 3 days.
You can set different duration formats.
You can export reports in CSV file format and open them in MS Excel.
You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

If you have any questions, feel free to schedule a demo with us.

Hope it helps.

Valeriia_Havrylenko_SaaSJet

Hi @Tom Rosenberg 👋

You have two options to see how long a ticket has spent in the different statuses

By JQL (Jira Query Language): You can use JQL to create a filter that includes both

the creation date and the resolution date of the issues. By constructing a query, you can retrieve the necessary data to calculate the resolution time. Here's an example of how you can do it:

<br>created >= "2023-01-01" and created <= "2024-01-31" AND resolved >= "2023-01-01" and resolved <= "2024-01-31"

Replace "start_date" and "end_date" with the desired date range. This query will filter issues created and resolved within that range.

2. By add-ons like Time In Status: This add-on tracks the amount of time an issue spends in each status. You can easily gat report about how long an issue was "open" and the exact date and time it was "resolved". Just simply:

Filter issues by Resolved
Set date range for issues.

Add-on developed by my SaaSJet team.
Let me know if you need further assistance with either option!

Ivan Garcia _Appfire_

Hi @Tom Rosenberg , welcome to the community

Unfortunately there's no built-in way of achieving this in Jira. Luckily, there exist some apps that can help you. I'd recommend our app Dashboard Hub Pro.

It makes it possible to track the time a ticket has spent in different statuses and calculate averages for groups of tickets. This app offers a comprehensive solution for your needs:

Time in Status Reports: Track how long each ticket spends in every status throughout its lifecycle. You can view this information in hours or days, depending on your preference.
Customizable Filters: Filter your reports by issue type, date range, assignee, and more to focus on specific groups of tickets, such as 'Bug' tickets raised in June.
Average Time Calculation: Easily calculate the average time tickets spend in each status, providing insights like the average hours spent in 'New', 'Open', 'Waiting for Engineer', etc.
Interactive and Visual Dashboards: Create visual and interactive dashboards that display your time in status data in a clear and understandable way. Combine these with other metrics and charts from 15+ product integrations for a holistic view.
External Sharing: Share your dashboards and reports externally with links, making it easy to communicate findings with stakeholders outside of your immediate team.

Highlight Image 2 - Cloud (2).png

With Dashboard Hub Pro, you can not only track the detailed status durations but also analyze and visualize this data to gain valuable insights into your project's performance.

I hope this helps you achieve the detailed tracking and reporting you're looking for!

Best regards,

Ivan

Tom Rosenberg

👍🏼

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud