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

Automation rule apparently not finding child issues of Epic

Tobias Lorenz_9gqlum

I want to clone an Epic with all children and have set up an automation rule.

The rule clones the Epic first, but fails to find all children of the Epic to cloning them as well.

I probably have a misunderstanding of the rules that I use.

Here is the Epic that I would like to clone:

Here is the ruleset:

And here is my automation log:

I also tried using various JQL queries, but this was not successful either.

Using JQL in the UI to search for children of this Epic works perfectly,

Any advice is very welcome.

Accepted answers

Tobias Lorenz_9gqlum

My research revealed, that the culprit here was the configured Issue Security schema on the Project.

Not only does the Project Role (atlassian-addons-project-access) need access to the project permissions. There also needs to be an Issue Security Level with this Project Role assigned, if Issue Level Security is used on a project.

All comments

K Vivek Rao

Hello @Tobias Lorenz Is it a full screen shot of the automation you configured? Automation works when you ask to perform action depending on triger.

Could you please share your requirement in detail?

Tobias Lorenz_9gqlum

Thanks for asking.

Yes, this is the full automation for now. I plan to extend it later.

I want the automation to clone an Epic, including all children of the Epic.

The automation is triggered manually.

As you can see in the automation log, it runs, but doesn't find very well existing children of the automation.

Bill Sheboy

Hi @Tobias Lorenz -- Welcome to the Atlassian Community!

Please try changing the branch type, from "Children" to "Stories (or other issues in Epic)"

Kind regards,
Bill

Tobias Lorenz_9gqlum

Hi @Bill Sheboy, thanks for your suggestion.

I already tried this branch type, but the result is/was the same. No child issues were cloned.

I then changed the branch type to "children", as recommended by the automation UI.

Bill Sheboy

Thanks for the reminder, as I ignored the Parent change for a moment. The Child branch type should have worked...

This seems to indicate the Parent field is not found correctly for those issues. Let's test that hypothesis:

Change the branch to JQL, with this:

parent = {{triggerIssue.key}} AND issueType != Epic

Also, what type of project is this: company-managed or team-managed?

Tobias Lorenz_9gqlum

It's a company-managed project.

Unfortunately, even if I change the branch to JQL with your suggested query, the automation still fails to find children of the Epic to clone.

If I use this very JQL to filter issues in the issues screen, the JQL works as expected. All 8 children are found. In the automation, they are not.

Tobias Lorenz_9gqlum

My research revealed, that the culprit here was the configured Issue Security schema on the Project.

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