I don't think it's possible to negate the permission (Project Role x does NOT have Create Issue permission), so I only see two options here:
1. Grant Create Issue to other roles except the one you want. However, this does not work if the user has two or more roles in the project (BTW, you did not mention a resolution for this case). Note that this will hide the Create Issue button.
2. Use a third-party plugin to add a validator to the Create Issue transition in your workflow(s). The validator should fail if the user has the specified project role. Note that this will not hide the Create Issue button, but instead will always show an error when the user submits the create issue form.
I’m a designer on the Jira team. For a long time, I’ve fielded questions from other designers about how they should be using Jira Software with their design team. I’ve also heard feedback from other ...
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