Latest addon does not allow an update of the 'Request participant field value.

With the older version of the automation addon, I was able to set a rule to update the 'Request participant' field by simply setting the corresponding customfield id (customfield_11256 which is locked by JIRA servicedesk) to say 'xxx@mmm.com'

Ever since the upgrade to V3.3.11, this rule has stopped working!

Error received: 

"Error editing issues
EQPHELP-106 (data was not an array (customfield_11256))"
 
wondering if the latest version is treating this field differently now. Would appreciate any help on this one.

2 answers

Edit issue syntax used (where customfield_11256 corresponds to the 'Request Participants' field:

{
"fields":
{"customfield_11256": "abc@def.com"}
}

Based on https://community.atlassian.com/t5/JIRA-questions/How-do-I-add-a-request-participant-using-Automation-for-JIRA/qaq-p/51130,

I ended up using the following and this resolved it for me. 

{
"update": {
"customfield_11256": [
{
"add": {"name": "mmm@nnn.com"}
}
]
}
}

Suggest an answer

Log in or Sign up to answer
Atlassian Community Anniversary

Happy Anniversary, Atlassian Community!

This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.

Read more
Community showcase
Published Apr 19, 2018 in Marketplace Apps

Calling all developers––You're invited to Atlas Camp 2018

 Atlas Camp   is our developer event which will take place in Barcelona, Spain  from the 6th -7th of   September . This is a great opportunity to meet other developers and get n...

366 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you