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

When Issue Is Mentioned in {{issue.description.body}} add as Linked Issue = Related

Vincent Lucero_qeovru

Context

I'd like to improve visibility across related issues by automatically associating them with one another when referenced in either comments OR description body.

Acceptance Criteria
When Issue Is Mentioned in {{issue.description.body}} add as Linked Issue = Related

Example solution in bottom image for solving this when {{comment.body}} contains regex as provided by Jira Cloud default template, but when I attempt to update this, JIRA restricts me to only link issues based on "Trigger Issue" or "Most recently created issue"

Screen Shot 2022-05-19 at 10.57.29 AM.png

Accepted answers

All comments

Mark Segall_iqztfr

Hi @Vincent Lucero - You could do something like this:

Create a variable to capture the key referenced in the description
Branch by JQL
- key = {{yourvariable}}
- Link to trigger issue

Bill Sheboy

Hi @Vincent Lucero

To use the Link Issues action to a smart value expression, type (or paste) the expression in the field and it will appear below the field. When finished typing/pasting, select the value below the field and it will be used.

This works for many of the actions which have a drop-down list of options for a target issue.

When you expect more than one issue to link, instead use the branching technique that Mark describes.

Kind regards,
Bill

Vincent Lucero_qeovru

@Mark Segall do you have an example of how to define variables in JIRA automation for a use case like this?

Mark Segall_iqztfr

Hi @Vincent Lucero - Taking a step back on this one. I think @Bill Sheboy has the correct answer for this. You should be able to set a smart value in your link. What does the audit log show for your rule?

Vincent Lucero_qeovru

I never implemented this rule since it wouldn’t allow me to select anything other the “trigger issue” or “last created”

I don’t know how to dynamically pass the value representing the Regex response of the mentioned ticket that triggered the automation in the first place.

Goal is to associate mentioned tickets in comments.

Welcome!

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

Quick Links

Find more posts tagged with

cloud

automation