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

Fetch a specific Linked Issue and copy to another custom field

Chris Delgado

Hi,

As the title stays, I'm trying to achieve the following using Automations.

1. If issue for example - RCA-#### links an issue (SS-####) as has the Concern

2. Fetch that issue key = SS-#### and copy the string into another custom field, let's call it Linked Issue Keys.

I have tried multiple automations but none of them seem to be able to fetch the linked issue I'm looking for.

I'm very open to ideas, I have also tried doing this in JMWE and using nunjucks but no sucess either.

Accepted answers

David Fischer

At which point are you trying to copy this field? During a transition? When the field value changes?

All comments

David Fischer

At which point are you trying to copy this field? During a transition? When the field value changes?

Chris Delgado

I want to copy this as soon as a ticket is linked as 'Has a Concern', it can be at any time.

Chris Delgado

David Fischer

In JMWE, you can use an Event-based action listening to the Issue Link Added event. Select the "Only apply to issues that match a Nunjucks condition" option and use this Nunjucks filter:

{{ context.issueLink.issueLinkType.name == "Issue Link Type Name (not direction)" }}

(replace the link type name with the name of the link type as it appears on the Issue Linking Jira admin page)

Then you'll use a Copy Issue Fields in the post-functions section, and select the appropriate From and To issues. For both, you'll use the "Issues returned by the following Nunjucks Template" option. Assuming "has the Concern" is the outgoing link direction name, you'll use these as the Nunjucks templates:

- Source:

{{ context.issueLink.sourceIssueId }}

- Destination:

{{ context.issueLink.destinationIssueId }}

And then select the field to copy.

If it erases the field on the "source" issue instead of copying the value, swap the two Nunjucks templates above.

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