I would like to create an automation to inform request participants to be append in the list

[Jader Peixoto Volkmer]

Hi guys,

I should create an automation in which I will inform the names of the request participants and theses people should be append in the current Request Participants field.

I have tried many ways with no good results.

Do you guys have a suggestion of how should I write this automation? 

Thank you

[Bill Sheboy · Accepted solution]

Hi @Jader Peixoto Volkmer 

For a question like this, context is important for the community to help.  Please post the following:

• an image of your complete automation rule in a single image for continuity
• images of any relevant actions / conditions / branches
• an image of the audit log details showing the rule execution
• explain what is not working as expected and why you believe that to be the case

Kind regards,
Bill

[Jader Peixoto Volkmer]

In this implementation I used:

Where I was trying to append JOICE to the request participants of the ticket. 

It didn't work.

2.Another try, is using Send web request:

I have tried to add Karen:

Using Send Web request:

Both cases are unsuccesfull.

Hope this information helps.

Regards,

Jader

[Bill Sheboy]

I recommend using one approach and trying to understand why it does not work, checking the audit log for problems.

Focusing on the first Edit Work Item action you show, you may select Request Participants from the dropdown list or use JSON to update it, but not both at the same time.

When you try to set just one participant with the dropdown field selection, what do you observe happening?

[Jader Peixoto Volkmer]

Hi Bill, 

sorry for the delay...

There is no problem when I select the participants with the dropdown selection. 

My point is that each type I run the automation with similar rule it wil overwrite the request participants already set in the ticket. I need to append the new ones.

[Bill Sheboy]

Thank you for confirming the symptom, @Jader Peixoto Volkmer 

To add additional Request Participants, please only use a JSON expression and not selecting the field from the dropdown list in the edit work item action.

How are you identifying the additional people to add to the Request Participants?  That information will be parsed to add to the JSON expression.

And, you will need to identify the custom field ID for your Request Participants field, such as by using this how-to article.

[Jader Peixoto Volkmer]

@Bill Sheboy to add additional people in the Request Participants I was thinking to do the following:

- create a temp custom multi user picker fileld to receive the names of the additional people. This field I called "Temp usr picker 2" that is "customfield_11515".

To add this people to Request Participants, I was thinking to use a JSON at the same automation rule:

{
"update": {
"customfield_10032": [{
"add": {"id":"{{customfield_11515.accountId}}"}
}]
}
}

Where customfield_10032 is the Request Participants.

The result is that it is not working well.

[Bill Sheboy]

You are quite close to the answer!  Your custom field is multiple-selection, and thus the values are iterated to add in the JSON:

{
  "update": {
    "customfield_10032": [
      {{#issue.customfield_11515}}
        {
          "add": {
            "id":"{{accountId}}"
          }
        } {{^last}}, {{/}}
      {{/}}
    ]
  }
}

Note the extra part to conditionally add a comma separator for each user except for the last one.  This ensures the JSON is valid for the rule.

And returning to my earlier question:

You now describe setting the users in a custom field, and adding those to the Request Participants.  Why not just add the participants when the work item is updated?

[Jader Peixoto Volkmer]

You could be right, but the point is that when I just use request participants in an automation to add new people to the ticket, the automation overwrite the people I already had in the participants. That's why I need to find out a way to append the new ones.