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: Find children of Epic, add their key to parent's comments

Fred_agblkk

I have an epic with issues in it. I'd like an automation that will:

- check if this epic contains issues

- add a comment with those issue keys

From there, another automation will add 'relates to' links to those issues.

The epics will eventually be converted to tasks, and I'd like to keep a link to the children.

Variations on this failed for me.

I'm an admin, and have scriptrunner if it helps.

Thanks for any pointers!

Accepted answers

Bill Sheboy

Hi @Fred

You note that you have an automation rule and that it failed to do what you wanted. Would you please post images of the rule and the audit log details, showing where it did not work as expected? That may help the community to offer suggestions. Thanks!

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Fred

Kind regards,
Bill

Fred_agblkk

Below is what remains. I scrapped the rest because it failed. Screen Shot 2022-04-29 at 4.28.21 PM.png

Bill Sheboy

Thanks, Fred.

That seems a bit different from what you described...perhaps that rule is assuming part of the problem has already been solved?

You noted two steps:

for an Epic with child issues, gather the child issues' keys into a comment. (I suspect you could also skip rule #2 and just add the links immediately.)
later after the epic has been converted to a Task, use the comment to add links to the previously child issues

Your first rule could be:

trigger: manual
condition: issuetype is epic
action: lookup issues with JQL of "Epic Link" = {{triggerIssue.key}} This assumes a company-managed project. Substitute "parent" for "Epic Link" if this is a team-managed project
advanced compare condition: check if there are any children
- first value: {{lookupIssues.size|0}}
- condition: greater than
- second value: 0
action: add comment, such as

"Here are the children to link later: {{#lookupIssues}}{{key}}{{^last}},{{/}}{{/}}

Fred_agblkk

Bill, that works perfectly, thank you! Has the syntax for this solution changed? It's not working on our instance, and seems like it's failed for others.

Screen Shot 2022-05-02 at 12.27.38 PM.png

It says 'The following issues did not match the condition:' which is the trigger issue.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

scriptrunner

cloud

jira-software

jira-software-cloud