Report for how many time spent for a task

[Orkhan Hasanov]

We need a report, but we are unable to generate it. The report should show the time elapsed between the creation of a task and when it is resolved.

For example, there is a project called "Satinalma."
In this project, we have custom statuses.
The initial status is "New Request," and the final status is "Delivered."

We need to know the duration between the task creation and when it is moved to the "Delivered" status, as well as when it is canceled.
This report is not possible with the default reports or JQL.
We are using the "Status Time Free" plugin, but it doesn't calculate correctly.

This report is essential for determining how long employees are spending on a task and, based on that, how many tasks were resolved on time and how many were delayed.

Could you please assist us in generating this report? Additionally, it should be calculated properly from a specific date (for example, from January) rather than from when the plugin is applied.

[Orkhan Hasanov · Accepted solution]

We can use Status Time Free plugin

[Mehmet A _Bloompeak_]

Hi @Orkhan Hasanov

Yes, you use Status Time Reports Free. If you have any questions, feel free to schedule a call with us.

[Rahul_RVS · Accepted solution]

Hi @Orkhan Hasanov 

As an alternative you can try out

Time in Status Reports 

With this app you generate time in each workflow status for multiple issues with multiple filter and grouping options. You can also extract trends analysis and add that as a dashboard gadget too.

The Time between Statuses report can help track time between specific statuses as per your requirement. Do give it a try.

More details here.

Disclaimer : I am part of the app team for this add-on

[Orkhan Hasanov]

Thank you !

[Ayça Erdem_OBSS_ · Accepted solution]

Hello @Orkhan Hasanov 

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 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. 

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. 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.

If you have any questions, let me know!

Ayça

[Orkhan Hasanov]

Thanks !

[Hannes Obweger - JXL for Jira]

Hi @Orkhan Hasanov,

an issue's status changes are captured in an issue's issue history, which you can access from the issue view in Jira or via Jira's REST API. From these status changes, you can calculate the time that an issue spent in a particular status - however it can be quite tricky to do that by hand.

That's the reason why a lot of users rely on solutions from the Atlassian Marketplace to do that for them. E.g., you may want to have a look at 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 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

[Orkhan Hasanov]

Hi @Hannes Obweger - JXL for Jira Thank you !

[Valeriia_Havrylenko_SaaSJet]

Hi @Orkhan Hasanov 

Also if you are open to try a marketplace solution, I recommend Time in Status can be a great solution. Add-on allows you to see how long each issue has been in each status or column, providing detailed reports on time in status, cycle time, and other key metrics. This can be especially helpful if you want a breakdown for each issue or need to analyze patterns over time.

   

Also look into Time Metrics Tracker | Time Between Statuses.  Add-on breaks down transition times between statuses in a more straightforward way, making it easier to track your team's efficiency and spot bottlenecks. Plus, it provides flexibility with exporting data and setting custom time metrics.

I hope this helps!

Add-ons developed by my team.

I hope you find this helpful 🚀

[Orkhan Hasanov]

Hi @Valeriia_Havrylenko_SaaSJet  Thank you very much !

[Eduardo Anflor - MindPro]

Hi, @Orkhan Hasanov 

I believe this information is not available in Jira standard gadgets. If you are open to try a marketplace solution, I recommend Mindpro Insights. I work at Mindpro and this app was developed to be simple and easy to use so everyone can create dashboards and share the information.

Just to illustrate with a simple example, I created a dashboard and added the "Time in Status" and "Cycle Time" gadgets as you can see below:

When you move the cursor over the chart segments, the system shows you the time each issue takes to be completed, per month:

If you click on that segment, the system adapts the entire dashboard to reflect the filter, so you can easily play with the metrics and drill down your data as per your needs:

There are over 50 gadgets you can choose from (Project, Agile, ITSM, Custom). Dashboards can be shared internally with your team. If you use JSM, you can also share the dashboards with customers via the JSM Customer portal.

I hope that helps.

[Orkhan Hasanov]

Hello @Eduardo Anflor - MindPro 

Thank you very much for the information.

To be honest, I spoke with Atlassian Support. I was informed that this functionality is not yet available in Jira without a plugin or an additional tool. Since I am a company employee, paying for an extra plugin was not accepted.

I used the Status Time Free plugin, but it was miscalculating. The reason was that the final status, "Delivered", which also represents "To Do", was continuously being counted. This report was supposed to show how long an issue remained in each status. However, since the final status remained indefinitely, the total time was miscalculated.

As a workaround, I applied the second-to-last status, which gave me a somewhat correct result. When calculating the total time an issue spent in each status excluding the final status, it provided the time spent on the issue.

[Marc - Devoteam]

Hi @Orkhan Hasanov 

This is not an option.

The app starts using data the time its active in your instance.

You could reach out to the apps vendor/developer, to see if there is a solution they can provide.