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

Linking Issues From a List to One Another

Matt Steadman_pjaqbe

Hi,

I am trying to come up with a way to accomplish the following using Automation for Jira:

- Issue is linked to multiple issues. (IE: Issue A links to Issue B, Issue C, and Issue D using as a Ships With Link)

- Issues that were linked to the single issue also link to the other issues as well. (IE: Issue B links to Issue C and Issue D using a Ships With Link. Issue C links to Issue B and Issue D using a Ships With Link. Issue D links to Issue B and Issue C using a Ships With Link.)

Currently I have come up with a way that when a issue is linked with the Ships With Link that a custom field will populate with all of the Issue Keys (the Issue Key of the Trigger Issue as well as all of the Linked Issues). I am then linking the other issues to all of the Issues Keys in the Custom Field.

The problem I am running into now, is that the automation does link the issues as it should, but, it does always throw the error of "You cannot link an issue to itself." (because the Issue Key for the Issue also resides in the list on the Custom Field).

My question is, is there a easier method that anyone has accomplished linking all the issues back to one another? Or, is there a way to ignore the error of "You cannot link an issue to itself." so that I will still receive emails when a rule fails after a success?

Attached are screenshots of the rules and error log

Thanks!

Accepted answers

nmenere

Hi @Matt Steadman ,

I spent an hour trying to come up with a solution around this but it is hard to remove the key from that string and still have it parsed by the link issue component. e.g. using

{{triggerIssue.Shipped With Keys.remove(issue.key)}}

results in

ABC-123, , ABC-234

If we had a "filter" mechanism on lists it could work, but alas, we don't.

Cheers,
Nick

All comments

Bill Sheboy

Hi @Matt Steadman

Please consider posting an image of your rule and the audit log for a case showing the error. This will provide some context for people to help out. Thanks!

I suspect that the solution to your use case will end up being selective about what values you put into that custom field, and so prevent the rule/tree from looping back on the trigger issue.

Best regards,

Bill

Matt Steadman_pjaqbe

Thanks Bill, I have edited the original post to include those screenshots

nmenere

Hi @Matt Steadman ,

I spent an hour trying to come up with a solution around this but it is hard to remove the key from that string and still have it parsed by the link issue component. e.g. using

{{triggerIssue.Shipped With Keys.remove(issue.key)}}

results in

ABC-123, , ABC-234

If we had a "filter" mechanism on lists it could work, but alas, we don't.

Cheers,
Nick

Matt Steadman_pjaqbe

Thanks for your time Nick.

Welcome!

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

Quick Links

Find more posts tagged with

jira-cloud

automation