Restricting edit to multiple groups

[Omar Bennani]

I've been following this guidance: 

How to restrict editing of an issue in a specific status | Jira | Atlassian Documentation

but I'm running into a hitch. How do I list multiple groups or roles to have edit access for a specific status. I've tried both groups or roles and using a comma separator like:

but that appears not to work. What's the right delimiter? It does look like it works when I only provide one value. 

[Trudy Claspill · Accepted solution]

Hello @Omar Bennani 

I believe you need to define a property for each value, adding a numeric suffix to each property key.

jira.permission.edit.projectrole.1 = 10076

jira.permission.edit.projectrole.2 = 10029

There is an example of this, the way it worked in Jira Server/Data Center, here:

https://www.j-tricks.com/tutorials/permissions-based-on-workflow-status

[Omar Bennani]

This worked like a dream! As a tip for someone else finding this note. 1. don't use generic suffixes like .1. It'll happily take a name like .product which will help tremendously when you're doing a group mapping which must use the extremely long ID references. Which, as a second tip, use the API method to get group ID like https://COMPANYNAME.atlassian.net/rest/api/3/group/member?groupname=atlassian-addons-admin

[Charlie Misonne]

@Omar Bennani 

This is actually great advice.

I think the docuementation on Use workflow properties could be improved to explain what [.suffix] is meant for