Hi everyone! Is there an automation to ensure that issues are only linked once with one link type?
For example, I have a duplicate automation rule so that issues with a similar description are linked with the "might relate to" link type, but it is also picking up issues that are already linked with other linked types like "split from", "relates to", and others. I want to avoid this.
Thanks in advance!
@Andrea Robbins, there isn't anything in Jira Automation that can ensure this. The best approach are to put the checks into your rules before they do the linking. Automation cannot stop links happening but they can detect duplicates.
Your best bet is to solve this by doing a check up front before you link them.
what are your thoughts on the automation shared below on my other comment below
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I'm not sure where you're planning on using it? As a guard?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I plan on using it so the same issue doesn't get linked more than once. I changed it to this since the one I had below had an error:
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
That makes sense. I think you can probably simplify it to:
issuekey != {{issue.key}}
However, are you trying to refer to the issue that triggered the rule or the issue with the similar description?
If it is the one that triggered the rule you should change your smart value to:
issuekey != {{triggerIssue.key}}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I think I might have a solution if anyone is familiar with reg expressions:
I keep getting an error though. I think my smart value is off maybe.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
For JQL the summary field does not support the IN operator. Instead you could try the contains operator: ~
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you! I am hoping the reg ex and smart values are correct and that the ~ was the issue.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Yeah, these kinds of Automations are efficient enough to identify the words, Jira is not an AI.
It's a Project Management tool. Link the issues manually you search through the duplicate issues and confirm whether they are exactly the same or nearly the same!!
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.