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

How to link issue when mentioned in the description field

Marcus_palm

Hi!

I'm trying to use Jira Automate to link any issue that is mentioned in the description field.

I already have a working solution for issues that are mentioned in the comments section. This is a template and it looks like this.

I tried to modify this into a new rule, for the description field. But for some reason it doesn't work. It looks like this:

Obviously I have made a mistake somewhere, but I can't figure out what. I tried with a lover case for "description.body" and "description.body.match" but that did nothing. Is the default description field called something else?

Sorry if this is a trivial issue. I'm not code with any type of code.

Any help would be appreciated!

Accepted answers

Trudy P Claspill

Hello @Marcus_palm

Welcome to the Atlassian community.

Instead of using {{Description.body}} use {{issue.Description}}

Comments are a special type of entity that have multiple attributes such as "body" and "author". The Description field doesn't have such extra attributes.

Also, within a rule when you want to access the data in an issue field you start the smart value by referencing the issue - {{issue.

...and then follow that with the name of the field - Description}}

All comments

Trudy P Claspill

Hello @Marcus_palm

Welcome to the Atlassian community.

Instead of using {{Description.body}} use {{issue.Description}}

Comments are a special type of entity that have multiple attributes such as "body" and "author". The Description field doesn't have such extra attributes.

Also, within a rule when you want to access the data in an issue field you start the smart value by referencing the issue - {{issue.

...and then follow that with the name of the field - Description}}

Marcus_palm

Hi Trudy,

Well, that was about as easy of a fix as I thought. Worked great!
Thanks for your quick reply!

Best regards

Marcus

Wael Bsaibes

Hello @Marcus_palm I am trying to perform almost the same automation as you. If an issue is mentioned or available in the issue description, have the automation link that issue to the current one. I can add the components created in your screenshot, but I cannot find the last action trigger that you included that says the following:

 
Then: Link issue to {{Descirption.body.match("[A-Z]+-\d")}}

(I am guessing it is the action that will take the issue mentioned and link it to the current one?)

I only have the 2 options from the dropdown menu:

Any guidance or advice is much appreciated

[EDIT]:

Ok never mind my first comment, I discovered that I can paste content in the dropdown field press enter and it remains there. That was the part I was not able to figure out.

In the end the automation didn't work as it considers the key not available in the description (1st screenshot) where we can clearly see it in the description (2nd screenshot):

----

@Trudy P Claspill your input is deeply appreciated. Thanks

Thanks a lot

Wael

Welcome!

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

Quick Links

Find more posts tagged with

cloud

jira-software

jira-software-cloud