Smart values not showing in email notification

[Megan Davis]

I am trying to use smart values to notify a asignee when they get a subtask assigned to them. I set up the automation rule and the email, but the smart values I entered are not reflecting in the email. Perhaps I have the wrong values? I want the email to give the name of the subtask, epic name it belongs to, and its due date. 

This is my automation code: You have been assigned task {{issue.field.summary}} for acquisition {{issue.epic name}}. This task is due on {{issue.duedate}}. 

Here is the email output: You have been assigned task for acquisition . This task is due on .

Any suggestions on the correct smart values I need? Thanks

[Bill Sheboy]

Hi @Megan Davis 

Smart values are name, spacing, and case-sensitive.  When in doubt of which smart values match your fields, please try this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

For example, the smart value for due date in an issue is {{issue.duedate}} however...

Your rule is triggered for the subtask when it is assigned to a person, correct?

If so, that means:

• the subtask's key is {{issue.key}} or {{triggerIssue.key}}
• the parent task's key is {{issue.parent.key}}
• and the grandparent epic's key is {{issue.parent.parent.key}}
• and the grandparent epic's name is {{issue.parent.parent.Epic Name}}

Please note: when using this syntax to progressively access parent and grandparent, all of the data (fields) may not be available.  For such cases, you will need to branch to the issue to access it.  I suggest try to access what you need this way first before resorting to branches, as your rule will become more complex.

Kind regards,
Bill

[Robert Wen_Cprime_]

Just out of curiosity, does the automation create the subtask?  Do we know if the subtask is being created?

The first one should be {{issue.summary}} 

The middle one should probably be {{issue.epic.key}} just to see if you're linking correctly.

Here's my reference on Smart Values: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-issues/

[Megan Davis]

Thank you for the link. The automation does not create the subtask. Subtask already exists and I just want to let the person assigned know that they have been assigned to a new subtask. I am wondering why the due date of the subtask didn't at least show properly when I used {{issue.duedate}}. Is that the proper syntax?

[Megan Davis]

I got the other values working with: You have been assigned task {{issue.summary}} for acquisition {{issue.epic.Epic Name}}. This task is due on {{issue.duedate}}. 

But it still isn't pulling the epic name. Just leaves that portion blank.

[Robert Wen_Cprime_]

How is the sub-task linked to the Epic?  Are you using Epic Link

I believe {{issue.epic.*}} only works with issues linked to Epics using Epic Link.

[Megan Davis]

I have the epic, then task, then sub-task under the task. So the subtasks are up under the epic. Is the subtask not already linked to the epic at that point? I am still learning Jira so I may be missing something with this. 

Thanks