Just a heads up: On March 24, 2025, starting at 4:30pm CDT / 19:30 UTC, the site will be undergoing scheduled maintenance for a few hours. During this time, the site might be unavailable for a short while. Thanks for your patience.
×Hi there,
I'm trying to do the following:
When issue is created based on conditions I set, I want to assign the ticket automatically to the "Reporting Manager", which is a custom field (customField_10683).
So, assignee = $customField_10683 is what I want to do.
It seems the only way to do this in Automations with JSON in the "Edit Ticket" action, but I can't wrap my head around the syntax.
Can anyone help?
Thanks,
Darryl
Hey Darryl,
No need to touch any JSON, we can do this very easily using a Smart Value:
This should work so long as the custom field is storing the user key.
Cheers,
Huw
Thanks Huw. That works great and is much easier than the JSON I did manage to get working, which was:
{
"fields": {
"assignee": { "name": "{{issue.customfield_10683}}"}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
I could really use a second pair of eyes and some advice please.
I have tried a number of different ways to achieve exactly what you list above, but each time the assignee field remains unassigned, despite the audit log showing success in the first case and error in the second, with the following notes:
1) issue already assigned to user
- configuration:
Assign issue > Smart Value > {{issue.customfield_10926.key}}
Assign issue > Smart Value > {{issue.customfield_10926.name}}
2) Error assigning issues CC-33: (Specified user does not exist or you do not have required permissions)
Assign issue > Smart Value > {{issue.customfield_10926}}
Assign issue > Smart Value > {{issue.customfield_10926.displayName}}
I've even tried the advanced route with JSON, and using variations of the above, with no success, the assignee field remains unassigned and the audit log shows issues edited successfully:
{
"fields": {
"assignee": { "name": "{{issue.customfield_10926}}"}
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Janine,
i had just the same trouble. The solution was:
{
"fields": {
"assignee": { "id": "{{customfield_10074.accountId}}" }
}
}
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.