Automation of Number of Issues in a Status

[Eric Gurin]

I am using Jira cloud and I would like to track when 'X" number of issues in a current sprint are in a particular status between the sprint start date and the 7th day of the sprint. Does anybody have a suggestion please? I am hoping to do this using Jira's out of the box cloud automation. Thank you.

[Eric Gurin]

Thank you Danut.

[Eric Gurin]

Thank you Bill!

[Danut M [StonikByte]]

Hi @Eric Gurin,

I'm afraid that this is not possible by using the Jira automation.

As Bill mentioned, you could try the Cumulative Flow Diagram report to see the number of issues in each status along the time, although I don't see an easy way to configure it to display only the issues from a specific sprint...

Another possibility would be to search on Atlassian Marketplace for an app that provides a report of gadgets that displays the info that you want.

In case you consider the idea of using an app, you could try the Cumulative Flow Diagram Chart gadget offered by our Great Gadgets app. It can displays the number of issues in each status along the time. 

You should configure it with a JQL that returns the issues from a sprint and set as timeline the sprint start / end dates, and to group data by 1 day.

Danut.

[Bill Sheboy]

Hi @Eric Gurin 

That information is in the issues' history, and it is challenging to access for the reporting you describe.

Rather than using Jira Automation, you could "hack" the Cumulative Flow Diagram / report by selecting your sprint timeframe and then de-selecting all the status values except the one you want to see.  This would show the count of issues in that status over time as an area chart.

https://support.atlassian.com/jira-software-cloud/docs/view-and-understand-the-cumulative-flow-diagram/

You could still use an automation rule to perform such counting, using repeated calls with JQL and the Lookup Issues action to count issues for the days of interest, and then store the results in created variables.  That approach will be slower and prone to errors (due to existing problems in status changelogs and checking them with JQL and the WAS IN operator).

Kind regards,
Bill