Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 21:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi all together,
I've got an automation rule triggered when an issue is linked, and I want the rule to delete exactly this new issue link when certain conditions are fullfilled (such as: wrong project, wrong type, wrong link direction).
Any ideas?
Please try using the Issue Linked trigger and testing these smart values with Issue Field and Advanced Compare conditions:
{{destinationIssue}}}
{{linkType}}
Kind regards,
Bill
Hi @Bill Sheboy ,
I know the smart values you mentioned and already use Advanced Compare conditions.
But there seems to be no way to find out the "direction" of the link (e.g. if A blocks B or the other way round).
And I couldn't find any way to delete exactly the (just created) wrong link within an automation rule, only an action to delete all links or all links of a certain link type and "direction".
So, in the meantime, I've tried to create another solution, which is to check either the links immediately when they are created or check them in a scheduled rule, and send an email, if the links do not fullfill my conditions, instead of trying to delete them.
See also: Are there Smart values to get the link direction i... (atlassian.com)
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that information. As @Trudy Claspill described in that other thread, some links have directions while others do not. The type of link and the triggering issue can be used to determine "direction" when it is relevant.
A possible workaround for deleting a single, specific link is to use the Send Web Request action to call a REST API function to delete the link with its link id value.
However, it may not be possible to get the just-added link's id when there are multiple links to the issues using an automation rule. In my testing with Jira Cloud, the trigger did not appear to supply that one; perhaps you can find it with your version of Jira.
If there is one-and-only-one link of that type, I hypothesize the link id could be found by filtering on the type from the issuelinks smart value in the trigger issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I have since added a suggestion to the other thread for checking the direction of the newly created link by looking at the Project values of the issues that get linked.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.