Hi, Trying to make a simple Jira Automation (conditional) rule that (if met) adds a label that contains a smart value of the inward related issue Example * Jira Story A* "relates to" linked Jira Story B * Action Code I have to add label with the condition met* { "update": { "labels": [{ "add": "tmsLink={{issue.issuelinks.inwardIssue.key}}" }] } } So this rule works as is if I only have one linked story (like above). But if I have multiple linked issues with different link types ("is cloned by" or "is blocked by" etc.) it fails to grab the issue id key. Is there a way I can specify in the json that I only want it to lookup/grab the related issue key that is "relates to"?

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

Smart value for linked "relates to" inwardIssue in Jira Automation rule

Sam Adams_josc3b

Hi, Trying to make a simple Jira Automation (conditional) rule that (if met) adds a label that contains a smart value of the inward related issue
Example

Jira Story A
- "relates to" linked Jira Story B
Action Code I have to add label with the condition met
- {
  "update": {
  "labels": [{
  "add": "tmsLink={{issue.issuelinks.inwardIssue.key}}"
  }]
  }
  }

So this rule works as is if I only have one linked story (like above). But if I have multiple linked issues with different link types ("is cloned by" or "is blocked by" etc.) it fails to grab the issue id key. Is there a way I can specify in the json that I only want it to lookup/grab the related issue key that is "relates to"?

Accepted answers

Trudy P Claspill

What is the trigger for your rule?

Can you show us the entire rule?

All comments

Trudy P Claspill

What is the trigger for your rule?

Can you show us the entire rule?

Sam Adams_josc3b

Thanks @Trudy P Claspill , included a screen shot. Trigger is "Issue Updated". Again, the trigger and or condition of the rule doesn't seem to be the issue.....and when I have an issue that has only one related linked issue this rule works fine. It's when I have multiple linked issues with different link types ("is cloned by" or "is blocked by" etc.) with in an issue that this rule fails

Trudy P Claspill

Hi Sam,

There is no screen image.

I asked about the trigger because if you were using the Issue Linked trigger that would give you access to both issues in the link pair.

I'll await your screen image before offering other guidance that might not be useful.

There's the screen image!

Bill Sheboy

Hi @Sam Adams

When you have multiple labels you want to add (for the linked issues), you will need an "add" clause for each one in the JSON. This can be done by iterating over the issue links in the list to build a JSON expression for each. Please try that approach and let me know if need more details.

Kind regards,
Bill

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-software

jira-software-cloud

atl-gruland

automation

smart-value