Time tracking Report

[Shmuel]

Hello,

I am looking for Jira built in solution for time tracking for tickets:
For example - how much time passed for ticket A from "To Do">> "Done" or for any internal statuses we use (E.g. "Ready for QA" to "QA Done" )

It should be for multiple tickets, so it's not an option to go ticket by ticket and to look at the history, and again no addons here... there is any options for that?

Thanks!

[Kristian Walker _Adaptavist_ · Accepted solution]

Hi Shmuel,

I can confirm that the time tracking reports that Atlassian provide are limited, so using an add-on on this requirement will not be entirely possible.

However, out-of-the-box  in Jira Cloud you can use the Dashboard Gadgets Jira cloud provides, as documented here  and the Time Since Issues Gadget and the Average Time in Status gadgets may help to give some details to help give some time tracking reporting.

I hope this helps.

Regards,

Kristian

[Shmuel]

Thanks!

[Emre Toptancı _OBSS_ · Accepted solution]

Hello @Shmuel ,

As others have pointed out, Jira has limited out-of-the-box capabilities for such a report. Use of a marketplace app is recommended.

I can recommend Timepiece - Time in Status for Jira which is built by my team at OBSS. 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. 

       

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. You can combine status times to see 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.

  

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

All these report types, including averages and sums, can be turned into charts.

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.

  

Timepiece - Time in Status for Jira

EmreT

[Shmuel]

Thanks.

[Mehmet A _Bloompeak_ · Accepted solution]

Hi @Shmuel

Unfortunately, there is no built-in solution for your need. If you prefer to use a free marketplace app, you can try Status Time Reports Free developed by our team. It mainly provides reports and gadgets based on how much time passed in each status (time in status, time in assignee, status entry dates and status counts, cycle time and lead time, average/sum reports by any field) and it is the limited version of Status Time Reports app.

Hope it helps.

[Shmuel]

Thanks

[Danut M _StonikByte_ · Accepted solution]

Hi @Shmuel ,

This might not be entirely possible without an add-on.

But if you decide to consider using an add-on, be aware that with the gadgets offered by our Great Gadgets app, you can calculate and display the average time between statuses in various ways. 

For example, the Control Chart gadget displays the issues from a filter by their cycle time, which, for instance, you can configure it to be the time between "To Do" or issue creation to "Done".

Hovering an issue in the chart, you can see details about it, like the cycle time.  As you can see the chart displays the Average line and its value.

You can set also a threshold value, to identify the issues that took longer than expected - the chart marks them in red.

An alternative to this is the Cycle Time Trend gadget that displays the average cycle time for past time periods (like weeks). This charts display the current average and the trend.

And these gadgets offers a Data tab with a report that you can easily export in CSV format.

 

For more details, see the articles from our blog.

With this app you can track projects of type Scrum, Kanban, SAFe, Service Desk, Customer Support, ITSM. So it can be a great asset for your team and company. 

Hope this helps. If you have any questions, please don't hesitate to contact us at support@stonikbyte.com. 

Thank you,

Danut manda 

[Shmuel]

Thanks

[Pradeep]

Hi @Eileen McEneaney 

As an alternative you can try out an app we have built for the same use case. 

Time in Status Reports 

The app has 20+ reports to meet a variety of requirements. You can also group your statuses to define your own cycle/lead times.

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

[Valeriia_Havrylenko_SaaSJet]

Hello @Shmuel   👋

As an alternative, you can try Time in Status for Jira Cloud developed by my SaaSJet team.

Time in Status for Jira Cloud can help track and analyze your team performance metrics easily, including how much time your team members spend on different tasks and how much time passed for ticket A from "To Do">> "Done" or for any internal statuses we use.

Also, you can export a report as XLSX or CSV files for further analysis.

This add-on is developed by my SaaSJet team and has a 30-day free trial version.

Please, let me know if you have any questions 😌

Best regards,

Valeriia