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; } } }

Ticket Time Tracking Report

Ushna Sarfaraz

I am working on a report, Where I am want to record ticket time spent in each status. The issue I am running into is I want to record the time of the ticket when it was moved to Sprint.
Status is To-Do when a ticket is created (any issue type), So I want to get the time when that ticket moved to Sprint.
and is it possible to use only build-in tools or JQL query that might help to fetch the data.

Accepted answers

All comments

Trudy P Claspill

Hello @Ushna Sarfaraz

If you wanted to use only native functionality for this you would need to create custom fields to track data and use Automation Rules to populate them.

It would be much easier to get time-in-status data using a third party app that already provides the tracking and reporting capabilities. There are several available in the Atlassian Marketplace.

Mehmet A _Bloompeak_

Hi @Ushna Sarfaraz

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.

App Features:

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.

Amay Purohit_RVS

Hi @Ushna Sarfaraz

You can use Jira Rest API's to build your own custom solution and track time spent by your issues in each status. For a readymade solution, a mktplace app can help here. 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 in hours/days to determine , how much time the issue spent in each status in the complete lifecycle of the issue.

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

More Details here

Disclaimer : I work for the vendor who built this app

Hannes Obweger - JXL for Jira

Hi @Ushna Sarfaraz

as you can see from the previous answers, this is an area where many Jira users rely on apps from the Atlassian Marketplace to fulfil their status time reporting needs.

If a Marketplace app is an option for you, I think you might like 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 - including all JSM-specific 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 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.

You may already know that you can trial any app for free for 1 month, so if an app is an option for you, perhaps try a few and see which one works best for you and your team!

Any questions just let me know,

Best,

Hannes

Gizem Gökçe (OBSS)

Hello @Ushna Sarfaraz ,

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. Status Duration Report in Detail.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 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.

Group By Created Month.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.

Tiimepiece 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. Also you can export the reports in to various formats easily.

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

Carla Ann Rowland

if you have add in script runner you can use status was functions for software project. The sprint function will also help. Did you check the native sprint reports?

I don't work for adaptavist it is just tool i use for this kind of report

Iryna Komarnitska_SaaSJet_

Hi @Ushna Sarfaraz
If you don't mind third-party apps, I can recommend the Time in Status app, developed by my team.

In it, you can generate a Time in Status report separately for each sprint.

2024-05-08_11-22-44 (1).png

Make pivot tables to analyze sprints.

2024-05-08_11-45-12 (1).png

The app also allows you to generate a separate Sprint Performance Report.

2024-05-08_12-08-06 (1).png

For you - 30 days of the trial. If you need additional consultations, we invite you to book a demo call with our specialists.

I hope this will be useful to you!

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