Automation for Jira Rule JSON help

Question

I am trying to make a rule that if a user isn't in a group when a security level is set, the user is removed from the field. We are able to get it to remove all users, but not the specified user based off the user picker field (multi-select)

We don't want it to clear all because some of the users are actually in the group

The JSON I have for clearing all is:

{
"fields": {
"Additional Assignees": [{
"set": ""
}]
}
}

I am pretty sure I need something more like

{
"fields": {
"Additional Assignees": [{
"remove": ""
}]
}
}

but I can't figure out the removal criteria

I have also attached the rule via screenshots

Aaron P_ · Answer

Hello everyone,
I know this topic is already old, but in case someone else can help and considering that after seeing all the documentation, all the comments about it and all the tests done using json, I only managed to add an individual user, when i put more than one user it just adds newest or gives error.

However there was a very simple way to do it that I tried and it is working correctly for me :)
You just have to create a variable and as a value add the Jira IDs of each user separated by commas, then you put that variable in the field you need and all the users are added.

In my case the field is called "Extra Assignees", a User Picker (multiple users) field, but the name doesn't matter ;)

In the image below, just change each IDJiraUserX to the actual ID of each user you have to add.

And then you just have to add this variable in the corresponding field:In case you retrieve them from a query via API or similar, instead you should put a foreach of the query in the value field:

This is so that it writes each value, if you see that it is not separated by commas add it after the {{value}}:

{{#VarQueryName}}{{value}}, {{/}}

Clark Everson · Answer

Hi Bill,

You nailed it spot on what we are trying to do. I will test this!

Best,
Clark

Bill Sheboy · Answer

Hmmm...Perhaps you can do this this after all in Server with two rules and a custom field (e.g. UsersToCheck), although the approach seems a bit brittle to me...And, I have not tried this so I recommend experimenting in a test instance.

Rule 1: creates the starting condition to check the Additional Assignees

* trigger: on change to security level
* action: set the the custom field UsersToCheck to the current value of Additional Assignees

Rule 2: simulates recursion and uses the custom field UsersToCheck to "burn down" a semaphore value.  In the rule detail settings enable Allow Rule Trigger so this rule can lead to its own firing:

* trigger: the custom field UsersToCheck changes
* condition: the custom field UsersToCheck is not empty  <<< This is the stopping condition for the recursion!
* if/else condition: treating the custom field UsersToCheck as a list, check if the first value is missing from the security group* action: update Additional Assignees to remove the first value found in the custom field UsersToCheck

* action: update the custom field to remove the first value from the list, and so fire off the rule again