Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


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

Im trying to calculate MTTR, MTTD and other incident timing metrics from the date and time picker cu

Im trying to calculate MTTR, MTTD and other incident timing metrics from the date and time picker custom fields, is there a plug-in available that will do this? or do I have to create a cool JQL query to accomplish this?  I also want to be able to put in a cool bar graph or dashboard that updates automatically as incident get created and resolved.








5 answers

0 votes
Bloompeak Support Marketplace Partner Dec 19, 2022

Hi @Anthony Martinez

Welcome to Atlassian Community!

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.

Hi @Anthony Martinez 

Welcome to the community !!

 If you would be interested in a mktplace app, you can try out our plugin, to get this data.

You can group your statuses to define your own Issue Age, Cycle Time, Lead Time, Resolution Time etc.

Time in Status Reports 

Disclaimer : I work for RVS, the vendor for this app


0 votes

Hello @Anthony Martinez ,

Presuming that all stages of the lifecycle of an incident and/or service are represented by workflow statuses on your system, I can recommend our app Time in Status that let's you create reports based on these status changes. 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. This report type also allows the user the exclude the times for "pause" statuses.

tisCloud_DBS_Metrics.png  tisCloud_DBS_Report.png

These reports show a list of issues by default so you can see the metric values for each issue separately. Also (for all numeric report types) you can calculate averages and sums of those durations grouped by the issue fields you select. For example total resolution time per customer (organization) or average resolution time per service, 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




If you might evaluate eazyBI app for Jira, please, check the demo dashboard with different use cases of how cycle/lead times can be reported with the app:



Janis, eazyBI support

0 votes
Gaurav Community Leader Dec 18, 2022

Hello @Anthony Martinez 

Welcome to the community!!

Jira Service Management natively provides the ability to track MTTA (Mean Time To Acknowledge) and MTTR (Mean Time To Resolve). These are based on the SLAs defined and have a report available.

In order to add further details likes Mean time to Detect and others, appropriate SLAs can be defined and tracked.

Alternatively, you can leverage plugins like EazyBI, which will help you create custom reports for this use case.


Suggest an answer

Log in or Sign up to answer

Atlassian Community Events