Forums

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

Error "No issues have a parent epic with key or name" in Jira Automation

Mandy Trickey
Contributor
February 16, 2024

In company managed project, running this automation to sum all story points in an epic/parent to show the total on the epic/parent. Getting this error. 2024-02-16_13-31-35.jpg

It runs pretty consistently but getting this error on some. 

2024-02-16_13-32-18.jpg

Not sure what it means or if there's some field missing or what. Would think if it's missing a field everything in that project would fail but it doesn't. Right now I only have one project that fails every time. Oh and when the rule fails, it changes the story points field value in the epic/parent to "None" even if there was previously a number value in it. 

1 answer

1 accepted

1 vote
Answer accepted
Mandy Trickey
Contributor
February 16, 2024

Well just figured it out for myself. You must make sure the Epic Name field is populated in the Epic/Parent where the total points are posting to. Once you populate that field, the automation runs successfully. Also, if you have more than one epic with the same name it will find all the issues with that epic name and add all the points up into the story points field even if from different projects. 2024-02-16_14-02-38.jpg2024-02-16_14-03-11.jpg

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.
February 16, 2024

Hi @Mandy Trickey 

Please note the Epic Name and Epic Link field are essentially sunset now in Jira.  The Summary and Parent fields are used instead.

I recommend updating your JQL for the lookup issues action inside of the branch to use 

parent = {{issue.key}} rather than "Epic Link" = "{{issue.Epic Name}}"

Kind regards,
Bill

Like John Funk likes this
Mandy Trickey
Contributor
February 16, 2024

Yes I saw they were going away. I will try the above change. Thanks!

Like # people like this

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
CLOUD
PRODUCT PLAN
PREMIUM
TAGS
AUG Leaders

Atlassian Community Events