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

Retrieving and using grandparent epic in automation rules.

Angie Adams

I am working on an automation to create a task from a sub-task. The tricky part is that I want the grand-parent of the sub-task to the be parent of the new task I am creating. I'm not sure how to retrieve the grandparent task to use it in an automation rule. Is this possible? and if so, how?

Accepted answers

Trudy P Claspill

Hello @Angie Adams

You should be able to use

to get the key for the "grandparent" issue assuming that the subtask is the rule trigger issue.

You could use that smart value to set the Parent field for the me issue you create. You may want to add a Log action in your rule to print the value into the log so that you can confirm the rule got the value you expect. You may also want to add a Condition to check that it actual has a value before you try to use it in your new issue.

All comments

Trudy P Claspill

Hello @Angie Adams

You should be able to use

to get the key for the "grandparent" issue assuming that the subtask is the rule trigger issue.

Angie Adams

Thanks, @Trudy P Claspill the value was actually logged, but the generating the task caused an error creating the issue "Could not find issue by ID or Key. (parent)

Angie Adams

@Trudy P Claspill I did some more testing & found that {{issue.parent.parent.key}} worked. Thanks for pointing me in the right direction. I haven't figured out the rhyme or reason for why triggerIssue works in same cases and in others it has to be issue.

Bill Sheboy

Hi @Angie Adams

The reason for that difference is the {{triggerIssue}} always refers to the trigger issue and {{issue}} is relative to the location in the rule flow.

For an example, please consider this sample rule...

trigger: some trigger with an issue ==> At this point, both {{triggerIssue}} and {{issue}} refer to the same thing.
action: some action
branch: on JQL to other issues
- action: another action ==> Inside the branch, {{triggerIssue}} and {{issue}} are different, where {{issue}} is now the branched-to issue(s).
action: an action after the branch ==> After the branch, both {{triggerIssue}} and {{issue}} again refer to the same thing.

For these reasons, it is helpful to post images of your complete automation rule and the audit log details with a question. They provide context to help the community offer better suggestions.

Kind regards,
Bill

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