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 count # of times resolved issue was moved to in-progress during its workflow?

Catherine Huang_q48snv

Hi,

I have a rule which increments a custom field that counts the # of times a current issue is moved to in-progress. I would like to apply this retroactively now to count the # of times resolved or completed issues were moved to in-progress during the course of their ticket open.

Is there a way to accomplish this using automation and without using plugins/add-ons?

Thank you

Accepted answers

Bill Sheboy

Hi @Catherine Huang -- Welcome to the Atlassian Community!

Short answer: you may need a marketplace addon or custom built app to count those values for historical issues.

More information...

Based on your response to John Funk, it appears you already have a solution for counting changes in future transitions.

For counting the previous, historical transitions, one could theoretically...

If issues had fewer than 100 total changes each, an automation rule could call the REST API function to get the changelog entries and parse them to count the number of times the issue entered an in-progress status from a not, in-progress status. This would likely need to be specific for each possible workflow if they differ by project.
This would be a slow rule if it ran for multiple issues, such as on a schedule to "catch up" the measure value stored in a custom field
Given you appear to be on a standard Jira license, this rule could quickly consume usage limits for the month, shutting down automation rules due to throttling

Other alternatives would be to build a custom application to count the values from the changelogs, again calling the REST API from outside of automation rules, or to investigate marketplace place addons which do the same types of measures.

Kind regards,
Bill

All comments

John Funk

Hi Catherine - Welcome to the Atlassian Community!

Typically, I solve this by creating a custom number field and don't put it on any screen (unless you want people to see it, then add it to the View screen, but not the Edit screen). Also, it is best to use a Default value of 0 for the field.

Then create an automation rule that is triggered by Issue Transitioned for your above scenario.

Finally, add an action for Edit Issue and update the custom number field by incrementing it by one each time the condition is met.

For the edit on the field use: {{ #increment }}{{ issue.My Number Field}}+1{{ / }}

where My Number Field is the EXACT name of your custom field.

Catherine Huang_q48snv

Hi, thank you for your response! I have that right now and it applies to each current issue that gets transitioned to in-progress, but I want to apply this to past issues.

For example, if I have an issue that I closed last, but it went back to in-progress 3 times, then I want to be able to run an automation that checks all closed issues and counts the # of times they want back to in-progress in the past.

Bill Sheboy

Hi @Catherine Huang -- Welcome to the Atlassian Community!

Short answer: you may need a marketplace addon or custom built app to count those values for historical issues.

More information...

Based on your response to John Funk, it appears you already have a solution for counting changes in future transitions.

For counting the previous, historical transitions, one could theoretically...

If issues had fewer than 100 total changes each, an automation rule could call the REST API function to get the changelog entries and parse them to count the number of times the issue entered an in-progress status from a not, in-progress status. This would likely need to be specific for each possible workflow if they differ by project.
This would be a slow rule if it ran for multiple issues, such as on a schedule to "catch up" the measure value stored in a custom field
Given you appear to be on a standard Jira license, this rule could quickly consume usage limits for the month, shutting down automation rules due to throttling

Kind regards,
Bill

Mehmet A _Bloompeak_

Hi @Catherine Huang

Welcome to the Atlassian Community!

Jira doesn't have a built-in solution for the report you mentioned. 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. To get a report of how many times the status of each issue is changed, you can have a look at Status Count And Entry Dates report. Entry date(see In Development, Ready for Testing, In Testing, In Development columns.) is status transition date and status count(see #In Development, #Ready for Testing, #In Testing, #In Development columns) is how many times an issue is entered to this status.

App Features:

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.

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

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

Hope it helps.

Metricus

Hi @Catherine Huang

If you're interested in a MarketPlace app, check out the Process Optimizer for Jira (built by my company - Metricus). It has comprehensive Time in Status and Activity reporting, as well as enterprise Process Mining capabilities to visualize your Jira workflows and processes. You'll be able to get the exact data you're after :-)

Process Optimizer for Jira

Ian

Amay Purohit_RVS

Hi @Catherine Huang

Welcome to the community !!

For historical transitions, as an alternative, you can take a look at our addon:

Time in Status Reports

The add-on provides the time in status of the entire issue workflow and there are 20+ reports in the app which help to meet a wide range of use cases.

One of the many reports is the Status Transitions count as shown below which will help in meeting your requirements.

Other details here

Do try it out.

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

TIS - STatus Transition Count.PNG

Hannes Obweger - JXL for Jira

Hi @Catherine Huang

welcome to the community!

As you've seen from the previous answers, there are a number of Marketplace apps that operate in this space. If an app is an option for you, your use case would be very easy and elegant to solve using the app that my team and I are working on, JXL for Jira.

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 number of times in [status], number of transitions from [status] to [status], and many more.

This is how it looks in action:

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. All this just works - it doesn't require any scripting or automation whatsoever, and therefore also doesn't affect your Automation budget.

Any questions just let me know,

Best,

Hannes

Gizem Gökçe (OBSS)

Hello @Catherine Huang ,

Welcome to the community!

As far as I understand, your primary choice is not a paid solution, but if you would like to evaluate it, I would like to introduce you to a very advanced tool with which you can easily access the reports/results you request. If you are OK with using a marketplace app for this, our team at OBSS built Timepiece - Time in Status for Jira for this. It is available for Jira Server, Cloud, and Data Center.

Time in Status mainly has several types of time reports (showing how much time each issue spent on each status, assignee, or group) but the app also has Status Count and Transition Count reports. These reports show how many times each status and each transition was used by each issue.

Report Types Status Count.png

Report Types Transition Count.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.

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 metrics measurement 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

Valeriia_Havrylenko_SaaSJet

Hi @Catherine Huang 👋

You can count number of times resolved issue was moved to in-progress during its workflow in 2 clicks it with Time in Status Just simply:

Choose Transition Count Report
Filter issues: Resolved

Знімок екрана 2024-04-08 о 11.19.30.png

Add-on powered by my SaaSJet team.
Have a nice day 👋 😊

Bill Sheboy

Hi @Valeriia_Havrylenko_SaaSJet

As a reminder...when recommending a marketplace vendor product, please ensure you disclose your affiliation to that vendor in your post wording. For more information about this, please see:

Atlassian Community online guidelines | Marketplace + Solution Partners | App Central

https://community.atlassian.com/t5/Marketplace-Apps-Integrations/Atlassian-Community-online-guidelines-for-Marketplace-and/ba-p/689723

Kind regards,
Bill

Valeriia_Havrylenko_SaaSJet

@Bill Sheboy
Thank you, Bill, for mentioning me! I have already made the necessary corrections.

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-service-management-cloud

jira-service-management