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

Help with automatically linking two jira tickets with matching labels

Mat Levell

Hey all, Ive been looking on the forums but haven't been able to get exactly what I need.
Im trying to link two issues (different project) of the contain the same label value. Im using Jira Automation and I was able to get my logic to run but its not finding the matched issue and in turn not linking. Screenshot 2024-09-23 at 2.00.30 PM.png Screenshot 2024-09-23 at 2.06.50 PM.png

Accepted answers

Bill Sheboy

Hi @Mat Levell

First, I notice what appears to be a typo in the JQL for your Lookup Issues action: there is a space between the period and the custom field id.

Next, you note the issues are in different projects. What is the scope of your rule: single-project, multiple-project, or global?

A single-project scope rule can create (or clone) issues in other projects, but it cannot access them otherwise. For the lookup to access issues in another project, and then link them, the rule must be multiple-project or global in scope.

Your Jira Site Admin will need to change the rule scope as it is changed in the global rule configuration area of Jira.

Kind regards,
Bill

said kouzibry

Hi,

What does the smart value {{triggerIssue.customfield_10301}} return ?
- Use a "Log action" with that smart value and see what it returns, then try a normal JQL search using the value returned, this might give you a better idea of what is happening.Something tells me the field "original vehicle id" is a text field, in which case you should use the operator ~ instead of =
The "For : Current issue" component looks off to me, I would use "For : JQL" instead

Here is an example of what I have in mind based on what I unserstood from your description

I hope this helps, let me know what you find out.

All comments

Bill Sheboy

Hi @Mat Levell

First, I notice what appears to be a typo in the JQL for your Lookup Issues action: there is a space between the period and the custom field id.

Next, you note the issues are in different projects. What is the scope of your rule: single-project, multiple-project, or global?

Your Jira Site Admin will need to change the rule scope as it is changed in the global rule configuration area of Jira.

Kind regards,
Bill

said kouzibry

Hi,

What does the smart value {{triggerIssue.customfield_10301}} return ?
- Use a "Log action" with that smart value and see what it returns, then try a normal JQL search using the value returned, this might give you a better idea of what is happening.Something tells me the field "original vehicle id" is a text field, in which case you should use the operator ~ instead of =
The "For : Current issue" component looks off to me, I would use "For : JQL" instead

Here is an example of what I have in mind based on what I unserstood from your description

I hope this helps, let me know what you find out.

Mat Levell

Thanks @Bill Sheboy the typo fixed the finding problem but now its not linking to each other. I suspect im doing something wrong with the branch and link.
Screenshot 2024-09-23 at 2.45.09 PM.png
Screenshot 2024-09-23 at 2.47.58 PM.png

Bill Sheboy

If you want to link those issues to the trigger issue, use a branch on JQL rather than the Lookup Issues action.

Mat Levell

Thanks @Bill Sheboy I got it working but if I use more than 1 label on the source issue it doesn't work. I source issue might have many labels that will link to a many issues in the other project. Screenshot 2024-09-23 at 3.12.25 PM.png Screenshot 2024-09-23 at 3.09.59 PM.png

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

automation