JQL differences between Advanced Search and Automation

[Mark Johnson]

"Epic Link"= {{issue.key}}

Advanced Search - returns all the stories with this issue as their Epic, ignoring Projects

Automation - returns stories with this issue as their Epic, from the same Project only

I want the Advanced Search result (all stories from any project) in Automation, using just JQL.
I am using the Lookup Issues component, then {{lookupIssue....  }}

Lookup issues

A search during custom value definition found no issues.

I've created the rule twice, once in Project and once in Global but neither works.
The Scope of the Global rule is "Software Projects"

Any suggestions?

[Tobias H]

Hi Mark!

I would suggest looking at Global Automations, as that can pull in data between two or more projects.

You are most probably working in the automation from within the Project setting, which limits the automation to within the project.

Let me know if you need me to expand on it :)

[Mark Johnson]

Thanks for the suggestion Tobias, but I've tried in Global as well as Project, with the same result.

[Trudy Claspill]

On the Rule Details page did you change the Scope of the rule to Multiple Projects and specify all the projects where the Epic and its child issues might exist? Or change the scope to All Projects or Project Category to cover all the projects where the Epic and child issues might exist?

[Mark Johnson]

I may have a permissions issue, but the Scope field is not editable.

It is either set to the Project when I create within the Project or set to Software Projects - which I assume means all Software Projects - if I create within the Global section.

[Tobias H]

The Scope field dropdown should look like this, if you have the permissions to change it:

[Mark Johnson]

It would appear that I don't currently have the permissions to change it, but as I said earlier even if I create a rule with access to all Software Projects then it still doesn't find issues outside the Epic project.

The global admin is OoO today (I am only admin for my project), so as a workaround I've simply moved all the Stories into my Project for the time being, but will have to move them back before actual development takes place.

[Trudy Claspill]

Only a Jira Admin can make a single rule applicable to more than one project.

I have tested (as a Jira Admin) that if a make such a rule and set the scope to Multiple Projects and specify  in the project list all the projects where the Epic and child issues exist, then the correct results are returned.

You also have to make sure that the Rule Actor has Browse Projects permission in all the projects, and that there are no Issue Security/Restrictions that would prevent the Rule Actor from seeing the issues.

[Mark Johnson]

I've not accepted any Answer because none of them work for me.

I got around it by moving all the relevant tickets into one Project. This breaks our development process but at least meant I could develop a Plan based on Epics having the correct rolled up value from Stories.

I'll have to move the tickets back to their original Projects once development starts.

I've discovered other anomalies with lookupIssues() w.r.t. Themes and Initiatives as well.

If I ever find a solution then I will post it here.