It seems when a behaviour has more than 1 case the plugin always defaults to the last rule in the behaviour when using "user in group restriction" and serverside script.
For example i have a field called Customer Code (its a Group Picker)
I do not want the customer to be able to set it (so its hidden), rather auto-populate on the creation of an issue.
So i create a behaviour and do the following for field Customer Code.
ServerSide Script: set Customer Code to a value("ClientX")
Then add a rule that says when user in group - "ClientX" alllow
I then add more rules below for each client (i can do this with more rules in 1 behaviour, or multiple behaviours). Whenever i create a ticket, all clients end up creating a ticket against the last rule (ie "Client Z"). Even if i put all the other clients as Except when in Group, it still picks up the last server side script.
I am using the server side script editor facility.
Hello Atlassian Community! Each month, we run a series of Spotlights to highlight Marketplace vendors and apps that our team thinks this Community would find valuable. In last month's Spotlig...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs