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.
The Jira Marketing team is putting together an ebook on migrating to Data Center. We're looking for pro tips on how you staffed your project team and organized your Proof of Concept. Share yo...
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