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; } } }

Automation to update field based on Linked Issues with Link Type "is implemented by" not working

Jason Gonzalez_316oc4

I'm trying to build an automation rule in Jira software which updates an Epic which only has linked issues under it (using the "is implemented by" link type), and it is not working. I don't know what I am doing wrong. I've followed all the instructions. The automation should look at the linked issues' Sprint Latest values that are linked to the Epic, and then update the "Estimated Completion Date Field Accordingly". It isn't even getting past the branch step.

Why is this happening?

What am I doing wrong?

See the attached screenshots.

Accepted answers

WirkKael

It might be an issue with how the branch is set up for linked issues in your rule. Sometimes Jira automation won’t pick up linked issues unless the link type is configured exactly as expected in the rule’s branch settings. You could try testing with a simpler condition first to make sure the branch is finding the issues at all before adding the sprint and date logic.

Bill Sheboy

Hi @Jason Gonzalez -- Welcome to the Atlassian Community!

Short answer: to update the Epic with the data from those linked work items, you will need to call the REST API to gather the issues first.

First, when using a rule branch, the actions you want to perform need to be inside of the branch. Please note the the area below the branch where actions can be placed. However, this will not help for your scenario as you want to update the Epic, and not the linked issues.

Often, to gather the data from a set of issues, one would use the Lookup Issues action with JQL. However, that will not work in your case because lookups for Data Center do not support the Sprint field yet. Here is the suggestion to improve that feature.

To solve your update of the Epic with data from the linked issues, the rule will need to call the REST API with the Send Web Request action. To learn more about that technique, please see this post: https://community.atlassian.com/forums/Jira-articles/How-Can-I-Sum-Up-Multiple-Issues-into-a-Parent-Number-Field/ba-p/2882712#M16701