This is the JSON I use for that purpose
{ "fields": { "customfield_10282": { "id":"{{triggerIssue.parent.reporter.accountId}}" } } }
I am getting "data was not an array" error message. But when I use assignee field it works well.
Can someone give an hand with this?
Hi @Esau Espinoza -- Welcome to the Atlassian Community!
Custom fields of People type are implemented as multiple-select, even when the single-user option was selected. This applies to all team-managed, or other project types, using People type fields.
The solution is to use the array format for the JSON, as the error message indicates. Here is the documentation for that format:
For example:
{
"fields": {
"customfield_10282": [
{ "id": "{{triggerIssue.parent.reporter.accountId}}" }
]
}
}
Kind regards,
Bill
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello @Esau Espinoza
Welcome to the Atlassian community.
Is this being used in an Automation Rule? If so, please provide screen images showing the entire Automation rule. and the details of the step where you are using this JSON code.
Also, please provide all the information from the Audit Log for the rule execution.
You have flagged your question as being related to the Jira Service Management product. Can you confirm that is accurate? Also, are you working with a Team Managed project or a Company Managed project?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Trudy,
Thanks for the help.
I attach the screenshots. It is a Team Managed project that use software project template
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.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thank you for the additional information.
Please provide screen images showing the entire Automation rule.
Is this execution of this rule was it your intention that MDP-196 be the editted?
What type of issue is MDP-196?
Does it actually have a Parent issue?
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.