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 Leaders.
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

 

2 answers

1 accepted

2 votes
Answer accepted
Bill Sheboy
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 Leaders.
April 30, 2021

Hi @Jeffrey Bistrong 

I think you are close, and just need a few adjustments.  A scheduled rule with JQL runs the steps after the trigger for each issue found, so it may be getting a bit of collision on the issues to check.

How about something like this below...  Please check the names of projects and issue types to confirm what I read from your image.

  • Trigger: scheduled every day with JQL of project = PS AND issueType = epic
  • Action: Lookup Issues on JQL of "epic link" = {{issue.key}} and issueType = risk
  • Advanced Compare Condition: {{lookupIssues.size|0}} is greater than or equal to 2
  • Action: do what you need, comment, log, transition the epic, etc.

 

Best regards,

Bill

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 Leaders.
April 30, 2021

Thanks bill, that looks good. I did end up figuring it out a little bit after i posted this, but I left it up here to see what would be posted. 

 

This is the solution I came up with which looks similar to what you did here except for the "size|0" part. Thanks a bunch!

Automation rules - JIRA 2021-04-30 18-56-27.png

Like Bill Sheboy likes this
Bill Sheboy
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 Leaders.
May 3, 2021

Hi, Jeffrey.  I am glad to learn you got it working.

The "size|0" adds a default value of zero when no issues match the JQL for the lookup.  I have seen problems where this can collapse to null, and so cause issues in rules.  So I add it for a bit of "belt and suspenders" insurance.  :^)

__Bill

Like # people like this
jonathank October 11, 2023

The missing puzzle piece. Thanks @Bill Sheboy , this comment helped me solve a different issue I was having.

Like Bill Sheboy likes this
0 votes
Melissa C January 22, 2024

@Jeffrey Bistrong 

Hello I'm looking to use your rule for a similar requirement. 

I'm looking to show the number of Tasks Open in an Epic. 

I've followed your example above but I'm not able to get it to work.

do you have any suggestions?

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 Leaders.
January 29, 2024

can you share the screen shots from your automation rule so I can see your logic please....

 

Here is a screen shot of a rule that I am using to confirm everything in an epic is done, sharing in the event it can help you revserse engineer it for your use. if not please share as much as you can and I can see if I can assist youMonosnap Automation - JIRA 2024-01-29 16-38-55.png

 

Here is a screen shot of a test rule I made that outputs the number of non-done issue in an epic, with the trigger being on the epic itself. The issue for you could be what the trigger issue is, are you triggering it from another issue on the epic or the epic itself. Please let me know and I will see how I can assist

 

Monosnap Automation - JIRA 2024-01-29 16-46-47.png

Suggest an answer

Log in or Sign up to answer