Is there an easy way to track how much time was spent on development through to completion?

[Janelle Seto]

I've been trying to pull up reports of development time spent on stories/tasks/bugs from development to completion but can't seem to get anything that comes back correct. There's "Resolved Date" and "Resolved" but I feel like this field is not always updated.

Alternatively, is there a default report template that can be used/configured to provide us with this info easily?

[Carlos Garcia Navarro]

Hi Janelle.

Have you checked the JIRA Enhancer Plugin? This may address your requirement to track time:

https://confluence.snapbytes.com/display/JEP/Duration+custom+fields

https://confluence.snapbytes.com/display/JEP/Time+Analyzer+custom+field

[Zoryana Bohutska _SaaSJet_]

Hi @Janelle Seto 

To the tools listed above, app Time Between Statuses can help you solve your request too. It tracks how much time was spent on development through to completion by setting the start/stop/pause timer preferences.

Also, using this add-on you can highlight overdue issues by setting time limits and export data you need.

[Ste Wright]

Hi @Janelle Seto

I would suggest ensuring that resolutions are set at completion. This is good for resolved dates - but also, to house resolutions (eg. Done vs Incomplete vs Won't Do).

If you're using a simplified workflow, you can choose to "set" the resolution to Done using the checkboxes in the appropriate columns from your Board Settings (3-dots icon on board > Board Settings > Columns).

If not, you'll need to be a Jira Admin and there are several options which you'll find in this Best Practises for Resolutions page.

With resolution set, there are a few options out there for measuring time:

• Created > Resolved Date: If this is the correct tracking metric, you could use these two data points in Excel or a BI Tools to calculate the time difference. You can use the Excel Connector to auto-update the data and results if you have Office 365 - see here.
• Control Chart: Use the Control Chart to show your cycle time or lead time. Details on the Control Chart are in this page - or a wider look on reports can be found here.
• Report Apps: Apps such as EazyBI for advanced reporting, or Time in Status / Time in Status for Jira Cloud
• Fields: Calculate the difference between two dates using a scripted field - such as using ScriptRunner
• API: Export the Issue History via the API and use the status transitions within it to create a view on time spent using a BI Tool. This isn't something I have alot of experience in but more details on the Cloud API can be found here.

Let us know if any of these would work for you :)

Ste

[Zoryana Bohutska _SaaSJet_]

Hi @Ste Wright 
Thanks for mentioning your Time in Status for Jira Cloud. Yes, in this case, our add-on can be the solution. @Janelle Seto to get such information that you require, it is necessary to create Status Groups. Using this tool the time spent in statuses you are needed will be added.

Best Regards

[Mehmet A _Bloompeak_]

Hi @Janelle Seto ,

You can use Status Time add-on. It generates status time report based on your working calendar.
 

If you are looking for a free add-on, you can try the free version, Status Time Free.

 

[Emre Toptancı _OBSS_]

Hello @Janelle Seto ,

Jira does not calculate status durations by itself. Our team at OBSS created Timepiece - Time in Status for Jira app for this exact need. It is available for Jira Cloud, Server and Data Center.

Using Time in Status you can report how much time each issue spent on each status. You can choose to include, exclude or combine certain statuses and you can add any issue field (including estimation fields) to this report so you can see estimations and actual durations side-by-side.

As well as statuses, you can report how much time each issue spent on each assignee or even each user group. The app also has two level reports that show status durations broken down by assignees or vice versa. 

You can get averages of those durations, grouped by any number of fields you pick.

You can produce reports based on the default 24/7 calendar or define your own business calendars with custom workdays and working hours. This is important because a report based ona 24/7 calendar does not make sense most of the time. Any issue that was opened on a Friday close to the end of business day and that was resolved early morning of next Monday will seem to be resolved in two and a half days on a 24/7 calendar which in fact is resolved in a few business hours. Custom calendars let you see that.

Time in Status also has reports that show how many times each status and each transition was used, and reports that show the date each issue transition to/from a date for the first/last time.

All data can be exported as XLS, XLSX, CSV.

Timepiece - Time in Status for Jira

Emre Toptancı

[Billie Shato]

Hi @Emre Toptancı _OBSS_ 

Does Time In Status only track time from when it's installed or will we able to view the same data on issues completed or in process prior to installing?

[Emre Toptancı _OBSS_]

Hi @Billie Shato ,

Time in Status uses the data in Jira issue histories to produce its reports so, YES,  you will be able to get Time in Status reports for issues created and completed before the app is installed.

EmreT

[Billie Shato]

@Emre Toptancı _OBSS_ Great, thanks!