Not able to set people field through automation in next-gen project

[bschmi]

Hi,

the setting is a next-gen Jira Service Management project where I created a field of type "People" and set it onto "Customer request form" (tested in Description fields and Context fields also).

As soon as I want to update it through automation it is not offered as an option.

The field is called "Close User" and all of the intention is to set the person doing the transition into this field by:

TIA! Birgit

[Martin Bayer _MoroSystems_ s_r_o__ · Accepted solution]

Hi @bschmi I played with it a little and I found out the only way it works is to switch to advanced mode (click "More options") and put this to the Additional fields field:

{
"fields": {
"customfield_10053": [ { "id": "{{initiator.accountId}}" } ]
}
}

YOu need to replace 10053 with your custom field's ID. You can get information about your custom fields using REST API

• https://your-domain.atlassian.net/rest/api/3/field
  • you have to replace your-domain with your domain

[Danish M]

@Martin Bayer _MoroSystems_ s_r_o__ 

I have a similar scenario wherein I have the same custom field (of type people) in parent and subtask. I do not see the option for this field in the drop-down and will have to use the Advanced fields. I want to copy the value for this custom field from parent to child. i have tried the following:

{
"fields": {
"customfield_10200": {{issue.customfield_10200.accountId}}
}
}

{
"update": {
"customfield_10200": {{issue.parent.fields.customfield_10200}}
}
}

every time, I'm getting Error while parsing additional fields. Not valid JSON.

[Ross F]

I can confirm there is a problem with setting a "People" field in this project type. The conditions do not work either. e.g. setting a condition for when this field type is "not empty" will never work. Seems to be a bug, and it remains unfixed a year later.

[Jack Nolddor _Sweet Bananas_]

Hi bschmi and welcome,

Can the action you are trying to automate  be done manually? I mean, is the field you are trying to set using the automation, editable at time point of the workflow by the actor you selected to execute the rule? I believe the field need to be editable or at least (not sure about this) being in the transition screen displayed during that status change.

Regards