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

Loop in Automation to a Parent of an Epic

Pancake

I am running Jira Data Centre not Cloud, so I know automation has slightly different features. We have an advanced heirachy set up, with Capability above Epic. I would like to perform an action on the Capability in the Parent Link when a trigger occurs on the Epic. I cannot figure out how to do this, is it possible?

eg:

Trigger: Epic Transitions

Loop ??? (this is the bit I can't figure out)

Add Comment to issue

Accepted answers

Pancake

As mentioned above finals solution is:

Trigger: Issues transitioned to Done

If: Issue type equals Epic

Loop: JQL: project = <capbility project> and key in parentIssuesOf{{{triggerIssue}})

Then Add a comment to issue: Test Comment

All comments

Marc -Devoteam-

Hi @Pancake

Welcome to the community.

Can you please share the config (screenshots) of your automation rule and details of the steps in the rule and the errors shown in the audit log (of there are any)

This will help community members to loo at your way of reasoning.

Pancake

There are no errors because I cannot figure out how to do this. The loop on parent option only seems to work for sub-tasks to tasks parent link, not on parent links introduced by an advanced heirachy.

John Funk

Hi Pancake - Welcome to the Atlassian Community!

You would use the lookup issues function in automation to "loop" through your issues. The Capability issue is still a "Parent" to the Epic. So use an automation trigger based on the Epic changeing and then in your Lookup Issues option, use:

Parent = triggerIssue.parent

Pancake

Hi John, thanks for helping, when I try this I get errors, I tried a couple of things, so a couple of errors below.

My automation is:

Trigger: Issues transitioned to Done

If: Issue type equals Epic

Then: Lookup Issues (see below)

And: add value to the audit Log: {lookupIssues}}

When I put {{triggerIssue.Parent}} or {{triggerIssue.parent.key}} in the lookup I get:

Log: a list of 100 issue keys from the project where I know the parent is. Results are limited to 100 and appear to be the 100 most recently created issues in that project