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

How to calculate time spent from Open To Closed

Shubham v

I have a workflow with states "Open, In Progress, In review, Done".

How to calculate the total time spend by a ticket from the time it was Created to DONE ?

Dont want to collect information on how much time was spend on each state, just want the total time since the ticket was created to it reached DONE state.

I am on Jira Cloud.

Accepted answers

Pramodh M

Hi @Shubham v

I've seen a lot of community questions around this requirement

Please follow the link to know how to achieve this,

https://confluence.atlassian.com/jira/tracking-the-time-taken-for-each-workflow-transition-126910724.html

You can choose which one suits you the better, but the plugin makes it easy to get the data

https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview

Thanks,
Pramodh

All comments

Pramodh M

Hi @Shubham v

I've seen a lot of community questions around this requirement

Please follow the link to know how to achieve this,

https://confluence.atlassian.com/jira/tracking-the-time-taken-for-each-workflow-transition-126910724.html

You can choose which one suits you the better, but the plugin makes it easy to get the data

https://marketplace.atlassian.com/apps/1211756/time-in-status?hosting=cloud&tab=overview

Thanks,
Pramodh

Mehmet A _Bloompeak_

Hi @Shubham v ,

As an alternative, you can try Status Time app developed by our team. It provides reports on how much time passed in each status as well as status entry dates and status transition count. Report can be exported as CSV, so that you can use external tools like Microsoft Excel or Google Spreadsheet to process the exported data.

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. It has various other reports like assignee time, status entry dates, average/sum reports(eg. average in progress time per project).

Here is the online demo link, you can see it in action and try.

If you are looking for a free solution, you can try the limited version Status Time Free. Hope it helps.

Emre Toptancı [OBSS]

Hello @Shubham v ,

If you are using Jira Software, Control chart in Kanban Board reports offer some visibility into this. It works with board columns rather that individual statuses and shows issues in a grouped chart rather than as individual issues. Custom calendar support is also limited but it can help you to get a high level report.

Alternatively, you need to do your own custom development. Since you are on cloud, you can't access the database so the option for you to get issue history data will be through REST API.

Beyond that, you can use a marketplace app to get the report you need.

For a ready built solution that offers great flexibility and details, our team at OBSS built Time in Status app for this exact need. It is available for Jira Server, Cloud and Data Center.

Time in Status allows you to see how much time each issue spent on statuses or assigned to each assignee. You can also combine statuses into consolidated columns to see metrics like Ticket Age, Cycle Time or Lead Time. Using this column consolidation feature, you can add a column to the report that includes all statuses in your workflow (except resolved and closed) and see the total time between creation and resolution of the issue.

You can calculate averages and sums of those durations grouped by issue fields you select. (For example see the total InProgress time per Epic, or average Resolution Time per issuetype).

Below are screenshots that shows a custom Lead Time field that shows the total of ToDo and InProgress statuses. The same can be done for any status combination.

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.

The app has Custom calendar support that your are looking for. This feature enables you to get your reports based on a 24/7 calendar or your custom business calendar. (This one is important because a 24/7 calendar in most cases shows misleading data. For example an issue created at 16:00 on Friday and was resolved at 09:00 on next Monday seems to stay open for 2,5 days but in terms of business hours, it is only a few hours. You can see this using Time in Status by OBSS.)

Finally, the app has History Trim feature. This feature allows you to report on a subsection of issue histories instead of the whole history. Very useful when you want to focus on changes made during sprint or project phase.

Using Time in Status you can:

See how much time each issue spent on each status, assignee, user group and also see dates of status transitions.
Calculate averages and sums of those durations grouped by issue fields you select. (For example see average InProgress time per project and per issuetype.)
Export your data as XLS, XLSX or CSV.
Access data via REST API. (for integrations)
Visualize data with various chart types.
See Time in Status reports on Jira Dashboard gadgets (released for cloud, server&DC gadget coming soon)

https://marketplace.atlassian.com/1211756

EmreT

Mariana_Pryshliak_Saasjet_qysy8m

Hello @Shubham v

Time in Status for Jira Cloud comes in handy in your case. It generates a report on how long an issue has been spent in each status.

In the "Total" column you can find the age of a particular issue. Is that what you need?

tis_total column (1).png

I hope you find it helpful.

Best regards, Mariana.

license management

Hi EmreT,

I am evaluating you plugin, as it seems really useful but can it handle linked issues/issues in epics?

Say a bug is found:

BUG-1 is created, walks around its workflow steps. It's judged that it's indeed a bug and is handed over to development to write a bugfix.

DEV-1 is created, linked to BUG-1, work is done, it passes it's workflow. A release is created.

DEPLOY-1 is created and linked to DEV-1. As the deployment happens, it passes it's workflow.

We would like to judge the flow of linked issues, from how much time was spent from the opening of BUG-1, to the deployment in DEPLOY-1.

We would also like to see the time spent in the individual tickets, preferably listed after eachother, so we can see which departments, statuses that held the process back.

Could your plugin help us with this, or at least parts of it. I did give it a go, and i can clearly see DEV-1, but i don't see if a week was lost between BUG-1 and DEV-1. I might be using the plugin wrong

Kind regards

Jonas

Emre Toptancı [OBSS]

Hello Jonas,

Our app primarily reports on individual issues. Reporting on linked issues is a little bit tricky. From a process perspective, I wouldn't recommend tracking this through multiple issues but that is a different story. Based on your current case you can try this approach if possible:

Create a text custom field (let's call it "Related Bug"). While creating DEV-1, populate this field with the key of the bug that caused this issue, in your case BUG-1. Also, enter the value BUG-1 to the Related Bug field of BUG-1 itself. This way, all related issues will be marked with the key BUG-1.

By default, Time in Status prepares List reports. Using the Aggregation button on the toolbar (The second one on the left, next to report type selection) you can switch to Average and Sum reports. In your case, you can use the Sum report type and select "Related Bug" field as the Group By field. When you do that, Time in Status will show each group (each BUG) as a row and the sum of all status durations for each issue group as row values.

Similarly (in a case that you don't use the Sum report but use List report) you can use the same Related Bug field to sort your data in the report so related issues will be listed next to each other.

This is probably not exactly like what you had in mind but these two options might help 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

atl-gruland