Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Dashboard - Show time between statuses



I’m looking for a way to show the time it takes a ticket to move from between a few different statuses.  The status it will be moving to is not a resolution, I need to see how long parts of our process are taking rather than the full cycle (created-> resolved)


I’m not looking to pay for any expensive plug ins but am open to reasonably processes plugins



5 answers

0 votes

Hello @Claire Lowry-Hubball ,

As others have pointed out, this is not available as an OOTB feature. You can try implementing this yourself or use a ready marketplace app for this. (The definition of a reasonable price is in the eye of the customer so I will leave that part to you.)

If you are OK with using a marketplace app for this, our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center. 

Time in Status mainly allows you to see how much time each issue spent on each status and on each assignee

tisCloud_StatusDuration_LeadTime_with Estimates.png  tisCloud_AssigneeDuration.png     

Time in Status offers two report types for your case:

The first one is Status Duration report (please see the screenshot above) which shows how much time each issue spent on each status. This report type has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements like Issue Age, Cycle Time, Lead Time, Resolution Time etc.

As an alternative approach, Time in Status also has Duration Between Statuses report type which shows the duration between two specific statuses.

tisCloud_DBS_Metrics.png  tisCloud_DBS_Report.png

For all numeric report types, you can calculate averages and sums of those durations grouped by the issue fields you select. For example total in-progress time per customer (organization) or average resolution time per sprint, week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) or sprints is particularly useful here since it allows you to compare different time periods or see the trend.

Time in Status 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. It supports both Company Managed and Team Managed projects.

Time in Status 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.

And the app has a REST API so you can get the reports from Jira UI or via REST.

Gadget_AverageStatusDurationByComponent.png  tisCloud_StatusDuration_LeadTime_Chart.png

Using Time in Status you can:

  • See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
  • Calculate averages and sums of those durations grouped by issue fields you select. (For example, see average InProgress time per project and per issue type.)
  • Export your data as XLS, XLSX, or CSV.
  • Access data via REST API. (for integrations)
  • Visualize data with various chart types.
  • See Time in Status reports on Jira Dashboard gadgets


0 votes
Bloompeak Support Marketplace Partner Sep 18, 2022

Hi @Claire Lowry-Hubball

As an alternative, 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.

  • 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, 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 free solution, you can try the limited version Status Time Free.

Note: If you are interested in cycle and lead time, you can have a look at the article below.

Cycle Time and Lead Time in Jira: Productivity Measurement with Two Critical Parameters

Hope it helps.

Hello @Claire Lowry-Hubball 

Although, you wrote about no paid solutions, but as an alternative, you can try Time between Statuses which is free for using for teams with up to 10 users. It shows the time each task has spent between statuses on the dashboard. 


This add-on is developed by my SaaSJet team.

I hope it helps

Thank you this I’m trialling this app now

0 votes
Rahul_RVS_Support Marketplace Partner Sep 06, 2022

Hi @Claire Lowry-Hubball 

If you are fine with a mktplace app, you can try out our add-on to get this data.

The plugin is also very reasonable priced.

Time in Status Reports 

The main features are as below

  • Multiple Time in Status Reports. Excel Export available for all status reports.
    • Time in Status
    • Time with Assignee
    • Time in Status with Assignee
    • Time with Assignee per Status
    • Status/Assignee Count
    • Multiple Transition Reports
    • Avg Time in status reports
    • Status Transition Dates Report
    • Time in Status Per Time Grain
    • Time with Assignee Per Time Grain
  • Status grouping
  • Save your reports
  • CSV Export
  • Multiple chart types
  • Dashboard Gadget


0 votes
Jack Brickey Community Leader Sep 06, 2022

Hi @Claire Lowry-Hubball , I think what you are looking for is "time in status". Unfortunately this info isn't able to be queried OOTB. What you could consider, although potentially quite messy, is to use custom date fields to record when an issue enters or exits a status. There are a number of community posts on being able to assess time in status. It might be worth searching and reviewing what others have done.

Thanks @Jack Brickey I’ve looked at a few referred to as ‘time in status’ but these focus specifically on how long a ticket sits in a status where as I’m more keen on how long it takes a ticket to move from status 1 to status 5 some of those tickets will go through statuses 2-4 or a variation of them 

Would time in status provide this as I’m struggling to see it 

Jack Brickey Community Leader Sep 06, 2022

The sum of TIS for a given transition path would give you this.

For example, let's assume you have the following statuses and that the "All" transition is used on every status - To Do, In Development, Ready for QA, In QA, Done. Now let's assume that a specific issue has a life cycle as shown below with the (TIS):

  1. To Do (1d 3h)
  2. In Dev (4d 6h)
  3. Ready for QA (2d)
  4. In QA (3h)
  5. In Dev (3d 1h) note the backwards progress, I.e. failed QA
  6. Ready for QA (2d)
  7. In QA (1h 15m)
  8. Done

So, as an example, if I want to know the time it took me from creation to ready for QA I would sum #1 and #2 = 5d 9h or 6d 1h based on 8h workday. I chose this specific example to illustrate that assessing these times can be misleading when you consider a backward transition.

Thanks that makes sense but isn’t really what I’m looking for.  I’d like the dashboard to do the work for us - No need for us to calculate anything 

Suggest an answer

Log in or Sign up to answer
Site Admin
Community showcase
Published in Jira Software

An update on Jira Software customer feedback – June 2022

Hello Atlassian Community! Feedback from customers like you has helped us shape and improve Jira Software. As Head of Product, Jira Software, I wanted to take this opportunity to share an update on...

5,042 views 18 32
Read article

Atlassian Community Events