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 the number of times an issue was returned to a specific status.

John Ricard

We are using the Kanban board template with JIRA Software (Cloud) in a Company Managed proejct.

There is a status called Planning and the workflow allows the issue to return to planning for additional information, new direction , etc..

We would like to have a count of the number of times a the issue was returned to the Planning status individually for each issue.

1) We would like this count to be displayed on the issue card for the specific issue on the Kanban board.

2) We would also like an aggregate total of all the times all the issues in the project have been returned to the Planned status and display this in a new field above he Kanban board.

Any ideas?

Accepted answers

Trudy P Claspill

I would suggest that you add a custom number field to the issues to hold this count, and use the Automation feature to increment the number each time an issue makes that transition. You can then build your reports based on that field, and display that field in the Card Layout for the board.

I am not aware of a way you can add to your board a display for the aggregate value of that field for all issues

All comments

Trudy P Claspill

I am not aware of a way you can add to your board a display for the aggregate value of that field for all issues

Bill Sheboy

Hi @John Ricard

Given the reporting needs you describe for your use case, you could try a couple of ways to solve this:

investigate marketplace reporting options, or scripting addons to increment a field
add a custom field for the counter, and use an automation rule to increment the field

If you are interested in the automation approach, the rule could be as simple as:

trigger: issue transitioned to Planning
action: increment the counter

To learn more about automation, please look at this documentation and examples:

Kind regards,
Bill

Avinash Bhagawati _Appfire_

Hi @John Ricard ,

With the help of JMWE Cloud app you will be achieve your requirement. Please find below detailed steps.

Create a custom field of number field type called "Planning Count" and it to target project screen. Please add it to only view and edit screen of the issues.
Add the "Planning Count" field to Board issue detail view.
For the transition that leads to planning status, you can add Set Issues Fields ( JMWE) post function and select Planning Count as field with below sample code. Note below example has been shown "Selected for Development" status and you can replace the status name with planning.
```
{{ issue | fieldHistory( "status") | filter({to_string: "Selected for Development"}) | length}}
```
So whenever you make transition to planning status, value will be set with help of JMWE post function.
Also please find below screenshot of kanban board.

Thanks,

Avinash

John Ricard

Hi @Trudy P Claspill,

Thank you for your response. I was able to create a custom field and use the automation to update each time the issue was returned to the Planning status per your suggestion.

I have also learned how to sum up the total of all the issues from a video by John Mckiernan but I have not yet figured out how to display the total on the menu at the top of the Kanban board.

Still looking for how to do that.

Thank you for the assistance.

John

John Ricard

Hi @Avinash Bhagawati _Appfire_,

I did have a look at the JIRA Misc Workflow Extensions (JMWE) I have been able to solve the basic issue without it. I did not see where it can change the menu on the Kanban board to add the new field that I want.

Thank you for the suggestion. Much appreciated. I will keep this in mind for future issue resolutions.

John

John Ricard

Hi @Bill Sheboy,

I did find this helpful and I bookmarked some of the pages I had not seen before.

Thanks again

John

Martins Vanags_eazyBI

@John Ricard

You might want to check out eazyBI app for custom jira reporting.

It can be used to calculate the number of transitions to a historical status and show that for all issues in the board and per issue. Also you can add "Time" dimension to filter transitions in time.

Martins / eazyBI team

Mariana_Pryshliak_Saasjet_qysy8m

Hello @John Ricard

You can try the third-party add-on that my company provides - Time in Status for Jira Cloud. It generates 7 types of status reports, including Status Count report, that shows how many times an issue has been in each status.

Also, you can export data from the grid to XLSX or CSV file, which you can analyze using such tools as Excel or Google Spreadsheets.

Hope you find it helpful.

Regards, Mariana

Rahul_RVS

Hi @John Ricard

For a readymade solution, 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

More than 8 types of 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 grouping
Save your reports
CSV Export
Multiple chart types
Dashboard Gadget

StatusCount (2).PNG

Mehmet A _Bloompeak_

Hi @John Ricard,

As an alternative, you can try Status Time Reports app developed by our team. It can display the time spent on specific statuses as well as status entry count.

It provides reports on how much time passed in each status. It has grouping feature so that by grouping statuses(In Progress → In Review → Done) you can get total time. You can also export the report as CSV and open it in excel.

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 by any field(e.g. average in progress time by project, average cycle time by issue creation month). And all these are available as gadgets on the dashboard too.

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

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

Garden16__h3vuuz

I need to keep a count of how many times the defect issue type was in particular status for a sprint or between mm/dd/yy to mm/dd/yy date range

1: Rejected

2: Reopened

How do I get report in JIRA that gives me a count how many times the issue went into Rejected status or How many times the Issue went into reopened status for particular sprint or between so and so date range.

Note : I have script runner plug in

Divya Srirangam_sox43m

Hi @Trudy Claspill

I have done the same, I have to count the transitions as below:
QA Progress - Inprogress

In Review - Inprogress

But I doubt it since I am using the "In Progress" status in both the automation rules" QA Progress- In progress" automation rule is not working, It automatically goes to 0 and then updates to 1 irrespective of the transitions-So basically it remains in "1". Gone through the audit log but still shows success

Screenshot 2023-06-28 152835.png

Screenshot 2023-06-28 152632.png

But in the below screenshot, it indicates some error which we cannot identify
Screenshot 2023-06-28 153017.png

Trudy P Claspill

Hello @Divya Srirangam

Am I reading the series of events correctly...?

Part 1:

The issue was transitioned from QA Ready to QA Progress.
The Issue Transition-QA to Dev was changed from 1 to 0.

Part 2:

The issue was transitioned from QA Progress to In Progress
The Issue Transition-QA to Dev was changed from 0 to 1.

The rule that you showed appears to cover Part 2. That makes me think there is another rule that is causing the field change in Part 1, if it is not being changed manually by a user.

You can click on the Rule Executions field in the Details panel of an issue to see what rules have run against that issue to find out which rule may have caused that.

You mentioned that you have two starting statuses that transition to In Progress and you are counting both of those. There is nothing inherently wrong with that if it meets your needs. In fact you could have one rule that includes both of the starting statuses in the trigger. Is your goal to count how many times the issue transitions to "In Progress" regardless of the starting status? Or are you trying to separate the counting of transitions based on the starting status?

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-software

jira-software-cloud

atl-orange