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 for inheritance of issuelinks field with "relates to" value only

David Exner

Hello community!
We can not achieve an inheritance of linked issues with "relates to" relation only from parent to child once a child is created.

We tried using smart values but could not find a way how to express it to the automation to get it to work.

You can see a draft of a rather general approach to inheriting any of the linked issues in the attached screenshot.

Could you please help us how to achieve it?

Thank you!

Accepted answers

Bill Sheboy

Hi @David Exner

You cannot directly set the issuelinks field only, as shown in your rule image. The reason is both issues which are linked are updated during the linking operation. And, I believe the REST API only supports linking two issues, and not one issue to many others. (Although I have not tested that.)

Instead consider finding the issue keys for the issues to link-to, and then using an Advanced Branch iterate over the keys and use the Link Issues action.

Kind regards,
Bill

All comments

David Exner

Bill Sheboy

Hi @David Exner

Instead consider finding the issue keys for the issues to link-to, and then using an Advanced Branch iterate over the keys and use the Link Issues action.

Kind regards,
Bill

David Exner

Thank you @Bill Sheboy ! We will give a try and let you know.

David Exner

Uff, so I am not sure whether I can achieve what we need to since it resulted in the successful run of the rule but the new issue was not assigned with any "Relates to" links while the parent has them. Any ideas, please?

Bill Sheboy

I am confused as what that rule is trying to do. For example, that created variable will produce a text string that looks like below, and then try to link that to another issue:

SEP, SEP, SEP = "Strategic Initiatives"

Would you please explain / confirm what problem this rule is trying to solve? It seems what you initially described is:

GIVEN an epic exists which has linked issues of type "relates to"
WHEN an issue is created which is a child of that epic
THEN link the same linked "relates to" issues to the new child issue

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-cloud