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

Smart values not working in the comments of the featured ticket that is linked to an Epic ticket.

Tom Goode_9hpsxh

I have an automation already linked to an epic ticket on creation. I created a second automation to grab the description from the already linked Epic and place it in the comments of the created ticket.

I know I can use smart values but none of them seem to work. It creates the comment section but leaves it blank where I entered a smart values. I have tried the following

I even thought it was a timing issue so I ran the comment automation after I linked the file.

Accepted answers

Bill Sheboy

Hi @Tom Goode

Context is important for automation rules...

Would you please post images of your complete automation rule, including details of the actions, and of the audit log showing the rule run? Those may help to explain what you are observing and which smart value expression will help.

Until we see those...

In some cases, issue smart values have information about the related issues, like {{issue.parent}} However those cannot be repeatedly drilled down into, lower (or higher) and so on. If they did, a single rule could potentially pull in all the data in the Jira site! Instead we often need to either branch to issues, or access them using actions like Lookup Issues.

Kind regards,
Bill

All comments

Bill Sheboy

Hi @Tom Goode

Context is important for automation rules...

Until we see those...

Kind regards,
Bill

Tom Goode_9hpsxh

Maybe I confused it with too much information. I have a custom field "StoreXXX"(Where XXX is the store number) in my user portal form and when they select it and submit, it links it to an epic that matches the store number. All I want is to show the description of that Epic in the comments field of the new ticket.

Tom Goode_9hpsxh

Bill Sheboy

Again without seeing your rule, I am guessing on the context of where in the rule you are trying to access these fields...

Let's assume the trigger issue is a Story, and that has an Epic parent.

For a company-managed project, the field you want is:

{{triggerIssue.epic.description}}

And for a team-managed project, epics are handled differently. That would be:

{{triggerIssue.parent.description}}

Tom Goode_9hpsxh

Here is the global automation below. Our epics are created for each store. This takes the store number {{store}} when value changes for store/DC. and uses it to link the ticket to the epic that matches the store number using. Thanks!

Epic 1.jpg Epic 2.jpg Epic 3.jpg

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