Hi there,
We want to remove all request participants in the portal when transitioning to closed.
I found this JSON, but it only removes a specific participant.
{
"update":
{
"Request Participants": [
{"remove" : {"id": "{{issue.assignee.accountId}}"}}
]
}
}
How to adapt it or is there another way?
Thanks,
H.
Hi Harald,
I don't think you need to use the JSON. Have you tried simply using the "Edit Work Item" action, then selecting the Request Participants field and simply leaving it empty?
Like this:
Try it!
@Jeroen Poismans yes, I tried this first but it didn't remove the participants - the automation then just does nothing
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Then you must be lacking some permissions (or the user performing the rule), because I have tested it once again on my instance and it works.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi @Jeroen Poismans thanks, you were right, it did nothing because of a wrong condition. So it works fine with leaving the field empty .
But out of curiosity: if it were permissions - which permission would it have been? Can't be "edit issues" as portal customers don't have this right but when closing it over such a customer testuser the removal worked too.
BR, H.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, it could have been several reasons:
Those are top of mind that I can think off.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.