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

Link issue when mentioned in the description field

Rachel Godina

Hello! I have been trying to create an automation that links issues when they are mentioned in the description field, and I'm having some trouble. I followed the steps taken from this previously asked question, but have been unsuccessful. I have an automation that works for linking tickets that are mentioned in the comments but even with changing the JQL to access the issue description body, the mentioned tickets don't link. I'm not sure if the issue is the trigger, but I would want it to check every time the issue description is updated.

Automation that I have currently:

Screenshot 2024-04-01 at 12.36.01 PM.png

I will also include a screenshot of what the automation for linking tickets in the comments looks like (this works perfectly):

Screenshot 2024-04-01 at 12.39.02 PM.png

Any help would be greatly appreciated, thank you!

Accepted answers

Bill Sheboy

Hi @Rachel Godina

The link issue action only takes one key, and so there could be challenges if:

there is no match
there are multiple matches
the match is to an issue key in another project (and the rule is project-scope)

I recommend writing that match expression on the description to the audit log to observe what it contains. That will help to diagnose what is happening.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Rachel Godina

The link issue action only takes one key, and so there could be challenges if:

there is no match
there are multiple matches
the match is to an issue key in another project (and the rule is project-scope)

I recommend writing that match expression on the description to the audit log to observe what it contains. That will help to diagnose what is happening.

Kind regards,
Bill

Rachel Godina

Thank you! I just took a look and it seems like the automation is activating, but does not do anything. The problem seems to be with the {{smart value}} condition - specifically the if condition (If: Compare two values).

Screenshot 2024-04-01 at 1.04.56 PM.png

This is what the ticket looks like (ticket names are not relevant). Test Ticket (blocked) is the ticket that the automation is running on (DS-744).

Screenshot 2024-04-01 at 1.06.15 PM.png

Bill Sheboy

Thanks for that information, Rachel.

When I try that match() expression it finds the issue key twice, due to the way the markup works.

The fix for that is to add distinct to return one key per issue:

{{issue.description.match("([A-Z]+-\d+)").distinct}}

Please note: if there are multiple issue references in the Description, the rule would need modifications to advanced branch over the values to add the links.

Rachel Godina

Thank you! I was able to try it and seem to be getting a similar problem as before:

Screenshot 2024-04-01 at 2.36.35 PM.png

This is the updated automation:

Screenshot 2024-04-01 at 2.36.53 PM.png

Do you believe that I would have to use the distinct parameter in the if condition?

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

jql

issue-link

description