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

Venkat/ Prabesh (Natera IT) August 16, 2017

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

0 votes
Venkat/ Prabesh (Natera IT) August 16, 2017

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"}
}
]
}
}

0 votes
Venkat/ Prabesh (Natera IT) August 16, 2017

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

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

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events