Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

Using the {{lookupIssues}} to find number of issues in an Epic

Jeffrey Bistrong
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
April 30, 2021

Really excited about the new Jira Work Management tool, and I am doing a POC for our professional services team to manage various projects with external customers by this team. 

 

I am looking for a way to automate a status change based on the number of "Risks" that have been identified. 

I have an epic for each project that is being worked on. If a risk is identified within that project, a ticket with issuetype = Risk will be created within the epic. 

 

I would like to automate the status change of the Epic, if there are 2 or more tickets (with issuetype = risk)

I have setup the following logic to try and return the number of risks within an epic, but it is currently not returning a value. I suspect because the lookup is inside of the (issue in epic)

 

Additionally, even the "{lookupIssues.size}}" within the branch is returning the total count, and not the count per epic

 

Automation rules - JIRA 2021-04-30 16-40-49.png

 

1 answer

1 vote
Nic Brough -Adaptavist-
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Champions.
December 17, 2013

You'll need to read your log to find out exactly why, but this is a common Jira startup problem when you haven't got a lot of resources allocated to it or you've got slow-loading plugins.

I've got http://blog.networkedcollaboration.com/2012/03/05/troubleshooting-jira-startup-errors/bookmarked to save me having to type the usual four things to try (they seem scattered in the Atlassian docs)

Suggest an answer

Log in or Sign up to answer