Using smart values in automation rules to pull in Parent data

[Rex Parsons]

Hello,

I have set up an automation rule in a project that creates six subtasks when the Story or Bug is created. and something isn't working correctly.  The team wants the summary from the Story/Bug parent issue to appear in the summary of the subtasks.

Here is a break out of the steps of the rule and the settings of the one that is failing:

In each action that creates the subtasks, I used smart values to pull the parent info into the Summary field.  Below are two examples of what should populate in the Summary.

Functional Testing - {{createdIssue.parent.summary}}

Business Comm - {{createdIssue.parent.summary}}

The rule works and creates all six subtasks, but the very first subtask that is created does not pick up the smart value.  That first subtask has the text, e.g. "Business Comms -" but not the smart value. The Summary is correctly populated for all of the rest of the five others as shown below.

I have switched the actions around and confirmed that it is always the first action that this happens to, so it is not something in the one particular action, but rather seems to be related with the order that they go in. The first one always fails to find the parent value.

Does the first action require something additional for it to find its parent? I have reviewed the action settings and tried switching between Current Issue and Trigger issue in the Parent field. I have tried a Re-Fetch before the first subtask is created. I have tried different smart values, like CreatedIssue,parent.summary, issue.parent.summary, triggerissue.parent.summary, createdIssue.summary, and nothing seems to make a difference.

It seems like the first action does not see the parent info, but after it is created, the rest are working ok. Need some assistance with this one. Thanks.

Rex

[Trudy Claspill]

Hello @Rex Parsons 

The details of the first action you have shown use the smart value {{CreatedIssue.Summary}}. That is not the same value you said you intended to use.

Functional Testing - {{createdIssue.parent.summary}}

Business Comm - {{createdIssue.parent.summary}}

If the trigger issue is always going to be the parent of the subtasks you are creating then you don't need to use {{createdIssue.parent.summary}} . Instead use {{triggerIssue.summary}}

[Rex Parsons]

@Trudy Claspill  That worked for me. Thank you. 

[Trudy Claspill]

You're welcome!

Please consider clicking on the Accept Answer button to mark your Question as Solved, if you have no additional questions on this topic.