Automation for JIRA overwriting Request participants on Issue Create

[Yusuf Adam Kwong]

Hi,

I am trying to have Automation for JIRA add Request Participants but it keeps overwriting them.

I have used 'Edit Fields', 'Request Participants', 'set value', in the text box ive tried 'Copy from issue', 'Copy from parent' and even 'Copy from Trigger Issue' in addition to the user I want added but it keeps overwriting them. In Issue History I would see request participants added from the CC in an email request but Automation would then remove them and replace with the user. 

Does anyone have any idea how to go about accomplishing this?

[Paul Krueger]

If you want to preserve the existing participants, you'll want to do it like this:

[Valentin R.]

@Paul Krueger How did you achieve this? I am trying to do the same thing for a custom fields (user groups) but it lets me choose either "copy from" or "set value". Can get both in one field like you have it.

[Valentin R.]

Hm, looks like it only works with the "request participants" type of field. Doesn't work the same with a user group field.

[Krishna Prasad]

Paul - You are totally awesome, fixed my issue . :)

[Julian Governale]

@Paul Krueger exactly what I was looking for since we add request participants when certain conditions are met but need to preserve the original participants. 

[Jo]

Hi @Paul Krueger , I tried your solution but it’s not working for me. The participants that were cc’d in the emailed request are being overwritten by the name that I put as the name to add to the list of the cc’d participants.

Do you by any chance know of another workaround?

@Julian Governale  are you also able to share your solution if it worked for you.

[Julian Governale]

@Jo  

I do the following for my situation which is different than the OP's questions but here is my rule. 

We use the assets in JSM to map key associates to applications or services.  If specific criteria is met during the intake of the request, those app owners/service owners are added as request participants so they are in the loop of the request. 

Trigger: Field change (Impact)

1. Capture Existing Request participants in a variable
2. Log the current Request participants to the log
3. Edit the request participants field and set the previous request participants (variable) and the Owned By users tied to the impacted service

For some background, Impacted Service is a custom assets object type field on our request type.  The owned by field is the user attribute of that field and that value needs to be included in the request/issue if the request or issues impact the company. 

Hope this helps!

[Jo]

Thanks @Julian Governale 

I will try that

[Parvaneh Zand]

Hi @Yusuf Adam Kwong ,

All options you've tried, are in Set Value operation.

You should click on '...' icon and select Copy From

and make sure Add to existing values checkbox is selected.

[Yusuf Adam Kwong]

Hi Parvaneh,

Many thanks for your response. However the above copies from another field. The rule I want to create is to add a specific customer to the ticket on create without overwriting the value.

Regardless I have tried creating a custom field, have that filled by another rule (rule B) on Issue Create and then use this rule (rule A) to copy to Request Participants but rule A always goes before rule B. Worse still, rule A with 'Add to existing values' still overwrites Request Participants when the custom field is empty. I only notice this behavior on Issue Create

[Zita Bagi]

Hi, I have the exact same problem right now and I haven't found the solution yet. :(

[Per Löfgren]

Same problem for me.  That checkbox "Add to existing values" seems to be bugged

[Steven Borne]

Hi everyone, I guess that no one find an answear to this problem :( ?

[Yusuf Adam Kwong]