Help assigning assignee in new issue created from a triggered issue

[Glenn A]

Nothing I've seen on the forum has worked... help!

• I have an automation that creates a new issue in project B when an issue in project A transitions to state x.
• I have a custom field ("DRI", cf[11111]) in project A's transitioning issue with a user
• I want the assignee in project B's new issue to get the user in project A's custom field

I've tried pretty much every combination of steps (assign, edit... set, copy) and always get the the new issue being unassigned and the same result in the audit log:

"Issue was already unassigned"

Which automation step, which field(s), and what descriptor gets me there?

help!

Thanks in advance buddies!!!!

[Glenn A · Accepted solution]

OK, got it!

I added the following in the 'then' block that created the new issue:

{
"fields": {
"assignee": { "id": "{{customfield_11111.accountId}}" }
}
}

thanks everyone!

[John Funk]

Hi Glenn,

Is this a Team-managed project or Company-managed project? Is the custom field a single user picker field or multiple user picker field? 

[Glenn A]

Hi @John Funk 

You might be onto something...  The custom field is multiple user (albeit I'm only testing with a single user in the triggers field). Interestingly, when I pull the trigger up on a JQL query and show both its assignee ad DRI columns, they do not appear the same... assignee shows the user's avatar while the DRI is just a link. Do I need to transform the type as part of the assignment?

Using {{triggerIssue.customfield_11111.accountId}} got me closer but still not there (log shows assigned but issue still unassigned).

Thoughts?

[John Funk]

Great! Glad you got it working. And just for clarity for future readers - are the projects team-managed or company-managed or a mixture? 

[Trudy Claspill]

Hello @Glenn A 

Can you confirm the source custom field is a user picker field?

You should be able to set the Assignee in the Create Issue action.

You can set it to a smart value.

{{triggerIssue.DRI.id}}

You might also be able to use the COPY option on the field. By default it will set the field as Copy from same field in Current Issue. You can click on that text together a pop to change the source issue to Trigger Issue, and change the source field. The source field does not always include all custom fields, but you might find your DRI field available to select.

[Glenn A]

Hi @Trudy Claspill 

This got me closer! I changed id to accountID but.... still not there! The audit log now says "Assigned issue to user" but when I look at the issue, it is still unassigned?! The custom filed in the trigger is a "people" field, I assume that is the same as a "user picker field as you asked (above)?

Thoughts?

[Trudy Claspill]

Sorry, yes, you're right. It would be accountId.

The People field is the Team Managed project equivalent of the User Picker field that is used in Company Managed projects.

I saw that you figured out the solution. Yay!