Automation: Smart Value to be used twice?

[Merrin Fulton]

Using the Channel> Portal > using a request type we fill in a custom field of XYZ: New Starter  (its a short text custom field and we fill in the name of the new starter)

In the automation - it recognises the request type a Task is created and the smart value successfully fills in the new starters name into the Summary of the new task.  The automation then creates a load of subtasks.

For only some of the subtasks, I'd like to assign the subtask to that same smart value (the atlassian user will have been set up in advance).  

The automation says it's run successfully  (and the new subtask is indeed created. Brilliantly, the summary of the new subtask includes the new starter's name has the name but the assignee is Unassigned). I've checked and what was in the portal is the same as what's registered in Atlassian. eg. Joe Smith was entered and Joe Smith is a valid user.

Am using {{Issue.XYZ: New Starter}}

Any ideas what's wrong? Or can we not use the same smart value twice on the same subtask?

TIA

[Alex Koxaras -Relational-]

Hi @Merrin Fulton and welcome to the community,

Users usually work with account ids and not with names. So instead of trying to assign the issue based on the name, you should use their respective account id to assign it.

[Merrin Fulton]

Hi Alex - thanks for the reply. When I choose an assignee from the drop down on the subtask within the automation - it works perfectly.  Am trying to use the custom field to save time and hassle. Unfortunately going off to find the account id will take more time than to manually change it.