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 need help with status history

Renata Ribeiro

Dear all, I need help creating a filter that identifies the average or total time that issues were in a certain status, for a specific project.

For example: I want to know how much blue project activities remained in test status, even though these activities have been completed.
The aim is to measure the time of issues by status, especially those that delay the process.

I await your response and thank you in advance!

Renata Ribeiro.

Accepted answers

All comments

Marc -Devoteam-

HI @Renata Ribeiro

That can't be done ootb, you will need a marketplace app for this, like:

https://marketplace.atlassian.com/search?query=time%20in%20status

David Nickell

I know there has been a plugin recommended and that very well might be your best alternative. I think it depends on your audience and features you want.

With that disclaimer in mind, I will point out there are REST API calls for getting the Changelogs (and transitions) for an issue. If your needs are simple and your audience is limited, you could use a REST API call like this:

https://jira.atlassian.com/rest/api/2/issue/JRACLOUD-79876?expand=changelog

provides tons of information including status changes

Created	From	To
2022-10-17T02:21:24.174+0000	Needs Triage	Gathering Impact
2023-11-08T04:30:49.185+0000	Gathering Impact	Closed
2024-03-01T21:34:22.342+0000	Closed	Needs Triage
2024-03-03T23:59:57.131+0000	Needs Triage	Gathering Impact

The disadvantages of setting up this capability include effort and the fact that it is outside of Jira (for example, it becomes part of a Power Bi dashboard)

The advantage is cost savings. Once you create this, your done.

Let me know if you want to pursue this further and would like some help.

Marc -Devoteam-

Hi @David Nickell

I do see and are also aware of this, but the topic is that it's also related to a single issue. Another disadvantage in my perspective,

You need to create an API call for each issue.

This can be solved of course by having a script and a table of issues in it an use variables to get the information for each issues, but you would need to update the table each time with new issues

Mehmet A _Bloompeak_

Hi @Renata Ribeiro

If you prefer using a marketplace app, you can try Status Time Reports app developed by our team. It mainly provides reports and gadgets based on how much time passed in each status.

Here is the online demo link, you can see it in action and try without installing the app. For your case, you can have a look at Time in Status for Each Issue report.

For further details, you can have a look at Status Time Reports How to Videos.

This app has a dynamic status grouping feature so that you can generate various valuable reports as time in status, time in assignee, status entry dates and status counts, cycle time and lead time, resolution time, average/sum reports by any field(e.g. average in progress time by project, average cycle time by issue creation month).

You can search issues by Project, Issue Type, Status, Assignee, Issue Creation/Resolution Date(and any other Date field) and JQL Query.
Status durations are calculated according to the working calendar you define. 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.
You can set different duration formats.
You can export reports in CSV file format and open them in MS Excel.
You can also add this app as a gadget to your Jira dashboards and reach “Status Time” from Issue Detail page.
You can enable/disable access to Status Time reports&gadgets and Issue Detail page per project, users, groups or project role.

If you are looking for a completely free solution, you can try the limited version Status Time Reports Free.

Hope it helps.

David Nickell

Hello and thanks for the response. I didn't have time yesterday, but spent about an hour today doing most of the work. I still need to add the datediff logic to know the actual amount of time per status. Then as you can imagine with a little bit of analysis we could determine which statuses were generally taking the most time.

I'll also add the worklog expansion I mentioned in another post so we can tell how much time people have reported per ticket.

Thanks again and look for an other update (probably before Monday). I'll try to publish my Bi Report so anyone interested can "touch and feel it".

Change log more.png

Gizem Gökçe (OBSS)

Hello @Renata Ribeiro ,

Sometimes it can be difficult, confusing and time-consuming to find your way through the built-in Jira gadgets and create a solution on your own. For specific needs like yours, it is better to use out-of-the-box solutions. If you are open to using an application specifically tailored to your needs, Timepiece - Time in Status for Jira which is developed by my team at OBSS, is the tool I would highly recommend. It is available for both Jira Cloud, and Data Center.

Time in Status mainly allows you to see how much time each issue spent on each status or 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 the time for multiple statuses to get metrics like Issue Age, Cycle Time, Lead Time, Resolution Time etc. Report Types Status Duration Report.png

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 to exclude the times for "pause" statuses.

Report Types DBS.png

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 team or average resolution time per sprint, epic, 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.

Group by priority.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 Jira, JSM and JPD 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. 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 reporting process. Enjoy a 30-day free trial to experience the full range of features.

If you wish, you can also schedule a live demo. We will provide a comprehensive overview of the application and address any inquiries you may have.

Hope it helps,

Gizem

Hannes Obweger - JXL for Jira

Hi @Renata Ribeiro

just to add to Marc's answer, here's how this could look in action in the app that my team and I are working on, JXL for Jira:

I'm using a status "Time in review" here, but you can configure any status(es) you would be interested in.

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 number of so-called history columns that aren’t natively available, including time in [status], time between [status] and [status], and many more.

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.

Any questions just let me know,

Best,

Hannes

Amay Purohit_RVS

Hi @Renata Ribeiro

If you are open to try out a mktplace app to get this data, you can take a look at

Time in Status Reports

One of the many reports which the app provides is Time in Status in hours/days to determine , how much time the issue spent in each status in the complete lifecycle of the issue. You can group your statuses to define your own issue resolution time. The app has 20+ reports to track your bottleneck Issues & Processes.

Disclaimer : I work for the vendor who built this app

Valeriia_Havrylenko_SaaSJet

Hello @Renata Ribeiro 👋

There is the Jira's native Days in column option, which shows the time an issue was in a certain status.

But if you need more details about the status time, you can try the Time in Status for Jira, which generates the average

and total time that issues were in a certain status, for a specific project.

Знімок екрана 2024-03-12 о 11.44.28.png

With add-on you can also easy:

filter data by the necessary criteria (assignee, project, sprint, epic, etc);
export report to CSV or XLSX files;
share report with analytical systems (Power BI, Qlik, etc).

This add-on comes with a 30-day free trial version and is free for up to 10 users.
If you have any questions, please don't hesitate to ask.

I hope this helps 😊

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