Jira Automation: Lookup Issues in another Project

[MrAldimensch]

Hey dear community,

I am in the process of setting up an automation and need help with it, especially with the lookup issues function.

What I'm trying to do:

After an issue transitions to “Done”, I want it to check if it is in an open sprint. Then it should check in another project (let's call it Project B) if an issue with the syntax “Component - {{Issue.Sprint.Last.Name}}” exists. I try to perform this check using the “Lookup Issues” function. If this particular issue exists in project B, it should link the trigger issue to the recently searched issue.

If this Issue in the other Project does not exist, it should create the Issue and link it.

So far, I was able to create the Issue in Project B. Unfortunately I'm struggling with checking whether this issue in Project B exists and thus the automation is always creating a new Issue. My desired behaviour is that the automation detects "oh there's already an Issue with this name" and links it instead of creating issues. According to the Audit Log no Isues are found within "Lookup Issues" and also when im verifying the queue with the exact sprint name. When im searching the same JQL, it shows up the target Issue. Can somebody help me? I attached some screenshots to provide some more clarity.

[Bill Sheboy]

Hi @MrAldimensch -- Welcome to the Atlassian Community!

What is the scope of your rule, listed in the details: single-project, multiple-project, or global?  I suspect it is single-project.

Rules with single-project scope may create (or clone) issues in other projects, but they may not access or edit them otherwise.

Please try changing your rule's scope to multiple-project.  Your Jira Site Admin will need to help with that as the configuration of such rules is done from global rule administration.

When doing this, carefully review your rule to confirm it only processes for the issues you want, perhaps adding conditions after the trigger to check the project.

Kind regards,
Bill