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

Is there a way to get smart values to print child issues in email?

Tom Mina-Coull

I am setting up an automation to send an automated email. The trigger is an epic being transitioned to Done. Is there a way to get smart values to print a list of the child issues under that epic as part of the email?

I would assume it would be something along the lines of {{issue.child.summary.,}} (with the comma being potentially the signifier of the separator in the list). I know there is {{issue.epic}} for going the opposite direction.

Accepted answers

Trudy P Claspill

Hello @Tom Mina-Coull

I have never heard of a "child" attribute on the issue smart value.

You could use the Lookup Issues action to get all the child issues of the Epic. The example shows how you can list out each issue in the results within an email.

All comments

Kathy Hart

Have you tried it without the period and comma at the end?

That may produce what you want.

Trudy P Claspill

Hello @Tom Mina-Coull

I have never heard of a "child" attribute on the issue smart value.

You could use the Lookup Issues action to get all the child issues of the Epic. The example shows how you can list out each issue in the results within an email.

Tom Mina-Coull

Hi @Trudy P Claspill

This seems like it would be the correct approach, but I am also somewhat new to Jira. From my understanding, you still have to give the lookup function a smart value to lookup, no?

The example shown on your link is {{#lookupIssues}} * {{key}} {{/}} where key is still a value that is used in many smart values. How do I get it to pull the child issues of the epic in question? Do I have to create some sort of log?

Tom Mina-Coull

Unfortunately not. Jira doesn't recognise the child attribute.

Trudy P Claspill

The example text shown is how you would print the list of issues that result from the Lookup Issues action.

The Lookup Issues action takes a JQL as the command for looking up issues. You can use smart values in the JQL in an automation rule. To find the child issues of a given epic the JQL should be

Parent = {{issue.key}}

(Atlassian is making changes to unify all project types to use Parent as the field in a "child" issue for noting its "parent" issue. This is a move away from using either Epic Link or Parent Link. The change may still be rolling out to your instance. See this for more information. If the change has not rolled out to your system yet you may need to use either Epic Link or Parent Link instead of Parent.)

Screen Shot 2023-06-28 at 9.39.20 AM.png

Tom Mina-Coull

@Trudy P Claspill thank you. This helped a lot!

Yael Bichovsky

I'm not sure if that's what you meant but assuming you have a cascading field you want to show, that's what worked for me (field name "TCode" for example)

{{issue.TCode.value}}, {{issue.TCode.child.value}}

So it shows the parent value and the child value.

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

jira-software-cloud