Getting a JQL from another project in automation

Question

I have two projects that works together. project 1 I use as a customer list, there I put all info regarding the customer, name, email, phone, address ans some customer preferences.

On project 2 I put all information about what I'm doing for them and at the end I send an email containing all what was done.

I want to use fileds from project 1 and project 2 in the same automation email. that way its easier to keep customer data up to date.

The problem is that when I run JQL on automation it only find issues on the current project. Is there a way to do that?

Antony Delgado · Answer

Hi!

Could anyone solve this? I have the same situation and I cannot obtain the data of the second project with which I want to interact

Is it really possible from a global automation to perform actions in project A depending on the result of a JQL that searches for information in project B?

Mauricio Cordeiro_m97f0w · Answer

Hi Rafael, you can do it changing your Rule scope on Rule details.

And then select Multiple Project ( on Scope) and in Project the list of projects you want to do the search

Andy Heinzer · Answer

Hi Rafael,

I see that you're using automation in Jira Cloud, and then using the lookup issues action.  When you create a project rule, then this action is limited to the scope of that project.  Meaning that all JQL searches have to be within that project (project=abc).  Hence when you are trying to use the JQL of

project=Cliente order by created DESC

This will never return any results when validated from a different project because essentially Jira is adding in the other project as a parameter such as

project=ABC AND project=Cliente order by created DESC

Since no issue can be in two projects at once the results will always be 0, unless you create that rule from the Cliente project itself.

This is something though that the global automation rules can help to overcome.  I tested this in my own Jira Cloud and I can confirm that creating a global automation rule with that lookup action does work when triggered/run from an issue in a different project.

You mentioned that you tried the global automation but that didn't work for you. Perhaps if you can share with us some more details about your trigger, conditions, branches, and action for this rule we can better understand the problem here.

Andy