Pull name of epic in automation

[Megan Davis]

I am trying to find the proper smart value to pull the name of an epic to include in an automation email.

I have: You have been assigned task {{issue.summary}} for acquisition {{issue.epic.Epic Name}}. This task is due on {{issue.duedate}}. 

And it's outputting: You have been assigned task 1Password accounts need moved to 1Password account for acquisition . This task is due on 2022-08-09.

Name of the epic should be after the word acquisition. Does anyone know the proper syntax to pull the epic name?

Thanks

[Mykenna Cepek]

I just tried this in our Jira Server instance:

{{issue.key}} has epic {{issue.epic}} named {{issue.epic.Epic Name}}

And the result was:

SAMP-17 was a Story, SAMP-16 was the Epic above that Story with Epic Name = "Make Coffee".

If that's not working in Jira Cloud, I'd call that a bug in Jira Automation. I searched and didn't see an existing bug.

Note that Stories, Tasks, and other Standard Issue Types are the only things that can use the "issue.epic" approach in automation. So if the example shown in the original post was running against a SubTask, for example, it would not be expected to work.

[Sue Wilson]

The {{issue.epic}} smart values only appear to work on tasks associated to the Epic, but not on the Epic itself.  I tried your exact config on an Epic, I got blank like you.  I tried it on a Story and got the Epic name, as expected.  Then, there's this:

https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

     "{{issue.epic}} -  Used to access information about an issue's epic.  This smart value only works for issues that have been added to an epic."