Issue Created vs Resolved Time Differences
6 answers
@Dilan Koyunoğlu Merhaba!
And welcome to the Community!
It is possible to track the time between issue creation and resolution in Jira, but Jira’s built-in features have limitations when it comes to calculating time in business hours. By default, Jira provides the Created vs Resolved Report, which shows trends but doesn’t break down the exact duration per issue.
If you’re open to using add-ons, you do have other options to consider.
Time Metrics Tracker | Time Between Statuses can be solution for you.
add-on provides advanced time tracking capabilities, including tracking time in business hours. Here’s how you can achieve this:
1. Create a new metric: Resolution Time (from Created to Resolved).
2. Define your work schedule, e.g., Monday–Friday, 9 AM–5 PM.
3. Choose Business Hours as a Format.
4. View the results as a table or export the data to CSV/Excel.
Also you can book a session with our specialist to see add-on in action 🚀
Add-on developed by my by SaaSJet team.
Hope this helps!
welcome to the community!
As you can see from the previous responses, this is an area where many Jira users rely on the apps from the Atlassian Marketplace.
E.g., your use case would be trivial to solve using the app that my team and I are working on: JXL for Jira.
JXL is a full-fledged spreadsheet/table view for your issues that allows viewing, inline-editing, sorting, and filtering by all your issue fields, much like you’d do in e.g. Excel or Google Sheets. It also comes with a long list of so-called history columns that aren't natively available, including the time between created and resolved, time in [status], time between [status] and [status], and many, many more.
This is how it looks in action:
As you can see above, you can easily sort and filter by your history columns, and also use them across JXL's advanced features, such as support for (configurable) issue hierarchies, issue grouping by any issue field(s), sum-ups, or conditional formatting. Of course, you can also export your data to Excel or CSV in just two clicks.
Any questions just let me know,
Best,
Hannes
Welcome to the community !!
Not sure if this information can be extracted out of the box. If you are open to try out a mktplace app, do take a look at
The app allows to configure your business days. Also the report "Time between status transitions" can help you calculate the time between two statuses considering your business hours. Do try it out
Disclaimer : I work for the vendor who built this app
@Dilan Koyunoğlu Hanım Merhabalar,
Atlassian Community'e hoş geldiniz!
This is not possible with native Jira capabilities, as Jira does not provide built-in tracking for business hours when calculating time between issue statuses.
However, you can achieve this with 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. Our app is available for both Jira Cloud, and Data Center.
With the Duration Between Statuses report, you can track the time between the opening and closing of a ticket while considering only business hours. Timepiece allows you to configure custom calendars, defining your working hours (e.g., 8-hour workdays) and excluding non-working hours, weekends, and holidays. The report then calculates the exact duration based on your business hours.
Timepiece - Time in Status for Jira is easy to set up and integrate with your workflows. You can try it directly from the Atlassian Marketplace, and our team is available to help with any questions you may have.
If you'd like to explore this solution further, feel free to check out Timepiece on the Atlassian Marketplace or schedule a demo with us for a walkthrough of the app's features.
Hope it helps,
Gizem
![Danut M [StonikByte]](https://avatar-management--avatars.us-west-2.prod.public.atl-paas.net/557058:2c7e3c8c-9a00-43c2-be60-99d0a1a9e5da/b4d0ffd6-e4fe-43f8-8000-723b8a08a28b/128 "Danut M [StonikByte]"){kind=avatar}
Hi @Dilan Koyunoğlu,
Welcome to the Atlassian Community!
The time between issue creation and its closure is a standard metric also called "lead time".
If you need this at a field level, you might be able to do it via automation. See https://community.atlassian.com/t5/Automation-questions/How-to-calculate-the-resolution-time-as-a-difference-between-2/qaq-p/1488447
If you need it as a report, you could look over the Cycle Time report, if available in your Jira project.
If you need it on a dashboard, Jira does not have such gadget. But if you are OK to use a plugin, you could try the Control Chart gadget offered by our Great Gadgets app. This gadget lets you calculate the lead time, cycle time, time-between two statuses, etc for the issues in a filter/JQL and it can also display a Data tab with a report with the time for individual issues, which you can easily export in a CSV format.
The gadget can calculate in days (of 24h). But, if it is useful for you, we could add an option to calculate in business days (of 8h). Feel free to contact us at support@stonikbyte.com if you have questions.
See also this article: https://community.atlassian.com/t5/App-Central-articles/An-effective-dashboard-for-Service-Desk-and-Customer-Support/ba-p/2360369
Danut.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.