Workflow property edit.deny.projectrole removes the permission from all users

Issue Summary

You can add a property to a status in a workflow when issues are in that status, users associated to specific project roles cannot edit the issue.

The format is described below:

• Property Key: jira.permission.edit.denied.projectrole
• Property Value: <id of the project role>

Currently, adding that property along with the id of any project role seems to be restricting the issue edition to all users in the instance, be they associated to that project role or not.

Steps to Reproduce

• In a workflow, select a status -> click on Properties:
  
• Add the values in the format as previously described, then publish the workflow:
  

You can get the id of a project role by hovering over the Edit button in the Project roles section of your instance:

Expected Results

Only users associated to that project role within the project will lose the ability to edit the issue in the status where the property has been added.

Actual Results

Everyone loses the ability to edit the issue when the issue is on that status despite not being associated to that project role in the project.

Workaround

If you still need to restrict issue edition in specific statuses, you can try the property jira.permission.edit.projectrole.

Instead of denying the permission to a role, you will grant the permissions to the roles you want to be able to edit the issue.

You can create multiple keys of the same property by adding an unique identifier to it: