In automation, how do I assign a task to a team member from a custom field

[Aimee]

Hi everyone, I've seen similar posts, read through Jira documentation to troubleshoot my issue but I'm a bit stuck so asking for help from the community.

Here's a screengrab of my automation, once I've created a task and upon popping it into a sprint I want it cloned and assigned to the person I've selected in a custom field called Design Assignee. The original task is assigned to someone else on the team as they work in pairs on the same project. 

Everything works up until the assigning element, I've also tried this syntax {{issue.customfield.xxxxxx}} but it also doesn't work. The custom field is a selection picker so I thought perhaps I need to change the selected team member from the picker into an account ID - as you can see in the screengrab but it also throws an error.

The error in the audit says "unable to assign the issues to the selected users" saying that "(Specified user does not exist or you do not have required permissions).

I checked my permissions and I have no permission issues. 

Hopefully I've given enough info, would anyone be able to help me resolve this?

Thank you, Aimee

[John Funk]

Hi Aimee - Welcome to the Atlassian Community!

Instead of doing an Assign Issue, simply add the Assignee field to the Clone Issue. Then for the Assignee field, click on the 3 dots and choose copy. Then choose Trigger Issue and the field you want to copy from the trigger issue. 

[Bill Sheboy]

Hi @Aimee -- Welcome to the Atlassian Community!

If you have the correct smart value or custom field ID for your field, using the accountId is the correct method.  Have you confirmed the smart value / custom field ID, such as with this how-to article: https://support.atlassian.com/cloud-automation/docs/find-the-smart-value-for-a-field/

Next, smart values are name, spacing and case sensitive, and when an incorrect one is used that returns as null.  The correct one is accountId: https://support.atlassian.com/cloud-automation/docs/jira-smart-values-users/#User-properties

Perhaps try this, after confirming your custom field ID:

{{issue.customfield_12345.accountId}}


Or, if the source is the trigger issue, use this:

{{triggerIssue.customfield_12345.accountId}}

Finally, you want to assign the newly cloned issue, correct? If so, the rule is missing a branch to "most recently created issue":

• trigger: value changes for sprint
• condition: sprint is not empty
• action: clone issue
• action: link issue to trigger
• branch to most recently created issue
  • action: assign issue

Kind regards,
Bill