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

I want to capture total days of an issue life cycle

BrentBot

I want to capture two points in time, that then produce a sum in a field when a project is closed out.

In that,

Data point 1: issue type is moved to 'in progress' state

Data point 2: issue type is move to `done` state

Can i capture those days and the summation is then put in a field

example: ticket is moved to in progress on tuesday (1/1/22) then ticket is moved to done state on thursday (1/3/22)

Custom field (Total days) >> automation inputs 2

Accepted answers

All comments

Pramodh M

Hi @BrentBot

Here's the answer to same requirement

https://community.atlassian.com/t5/Jira-Software-questions/Getting-average-time-difference-between-2-status-changes/qaq-p/1477620

Thanks,
Pramodh

BrentBot

@Pramodh M i dont think this answers my question. i want to calculate the days across different statuses; more so i want track statusCategory

You have the question answered, you need a plugin in order to achieve this or automation for Jira as an alternative to calculate the time between Issue created and Issue resolved (With Automation for Jira, statusCategory time cannot be achieved directly)

One such plugin is Time in Status Plugin

Again linking similar discussion here

https://community.atlassian.com/t5/Jira-Software-questions/Automation-for-Jira-Ability-to-get-the-previous-transition-date/qaq-p/1680739

You'll end up creating custom fields just to track the time and managing the rules!!

Let me know if you have any query

Thanks,
Pramodh

Rahul_RVS

Hi @BrentBot

If you are ok with a marketplace app to get this data you can try out our app.

Time in Status Reports

The add-on provides the time in each status for the entire lifecycle of the issue and you can filter by issue type as well. You can also combine your statuses to define your lead/cycle/resolution time and also extract the transitions history of the issues. The main features of the app are as below

Multiple Time in Status Reports. Excel Export available for all status reports.
- Time in Status
- Time with Assignee
- Time in Status with Assignee
- Time with Assignee per Status
- Status/Assignee Count
- Multiple Transition Reports
- Avg Time in status reports
- Status Change Dates Report
- Time in Status Per Time Grain
- Time with Assignee Per Time Grain
Status grouping
Save your reports
CSV Export
Multiple chart types
Dashboard Gadget

Disclaimer: I work for RVS, the vendor for this app, and I am one of the developers of the app.

Emre Toptancı [OBSS]

Hello @BrentBot ,

The data you need is available in each issue's history but Jira does not give this as a ready-to-use report. The closest you can get is using a Control Chart or a Cumulative Flow Diagram. Both are available as part of Jira Kanban Boards. They paint an overall picture but they don't give you the chance to work with individual issues. They also have limited flexibility in terms of report parameters.

To get what you want, you need to use a marketplace app. Our team at OBSS built Time in Status for this exact need. It is available for Jira Server, Cloud, and Data Center.

Time in Status basically allows you to see how much time each issue spent on each status and on each assignee.

tisCloud_StatusDuration_LeadTime_with Estimates.png

The app has Consolidated Columns feature. This feature allows you to combine the duration for multiple statuses into a single column and exclude unwanted ones. It is the most flexible way to get any measurement you might want. Measurements 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 (organization) or average resolution time per week, month, issuetype, request type, etc. The ability to group by parts of dates (year, month, week, day, hour) is particularly useful here since it allows you to compare different time periods or see the trend.

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

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 issue type.)
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

Timepiece - Time in Status for Jira

EmreT

Karolina Wons_SaaSJet

Hello @BrentBot

I'm not sure whether you can get it without the third-party add-ons, but as an alternative, you can try a Time in Status for Jira Cloud. It generates 7 types of status reports, including a Status Entrance Date report. It shows the date an issue has entered each of the statuses.

A Time in Status report shows how long an issue has been spent in each status. In the "Total" column you'll get the total time for all statuses.

Is that what you're looking for?

This add-on is developed by my team and is free for using up to 10 users. So let me know if you have any questions.

Oskars Laganovskis

Hi @BrentBot ,

I see that you have already been offered several solutions for reporting and tracking Issue life cycle.

If you are looking at marketplace apps - I might suggest yet another reporting app - the eazyBI app for Jira that allows creating simple reports and completely customized reports as well.
It allows one to see the totals and averages on the project level and also drill through assignees or projects down to each issue.

Not only do you see the figures after the project is closed - you may monitor progress already during the project and identify the upcoming trouble.

You may check the Demo account showing the dashboards created with eazyBI. The Jira Issues dashboard seems to cover a bit more than your use case:
https://eazybi.com/accounts/1000/dashboards/4553-jira-issues

Another report showing details on the issue level:
https://eazybi.com/accounts/1000/cubes/Issues/reports/144357-status-changes-for-issues-in-progress

You may play around to find the view that suits you best and explore the collection of already available reports.

The app is available for a 30-day free trial, so you can make sure it fits your needs before making any commitments.

Kindly,
Oskars, eazyBI support

BrentBot

Does anyone know if this is possible through Tempo since dates and times are being captured?

Bill Sheboy

Hi @BrentBot

You mentioned me for input on this question, so...In my opinion:

Jira could do a better job managing and measuring team's workflow;
This is why there are so many vendor addon products to enhance this area;
I suspect that as Jira does not appear to manage workflow change in histories, built-in or addons cannot show measures spanning such changes...changes which are a normal activity for improving teams over time; and thus
Other than for a trivial, stable workflow (backlog, in progress, done)...customers need to take additional actions.

First thing, please consider what problem are you trying to solve and what measures do you need to help? Understanding that will help decide if you should: export your data to report elsewhere, purchase one (or more) addons, use Jira automation/REST API/web hooks to help, etc.

You seem to want to measure the days an issue was in progress, regardless of status. That can be done with a custom field and scheduled automation rule to capture Age of WIP. The last value set would be close to your answer...depending on the schedule frequency. The same thing could be found by reviewing a single issue's history in the UI, or by calling the REST API repeatedly to parse the history.

You then seem to note adding those values, perhaps across issues. I do not understand what that would help answer for workflow...perhaps you could explain further.

Thanks, and kind regards,
Bill

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