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

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?

Accepted answers

All comments

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 P 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.

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.

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-cloud

automation