I'm running JIRA over the cloud with different end clients having their own projects for issue management. Currently I've got users assigned to groups and then the groups assigned to project roles. When a project is created, I am using a project template that is tied to the project roles.
So what is happening...
When an end client clicks on the project listing, they can only see their project. Entering in another project they don't have access to doesn't show up in the autocomplete and as far as they know, there are no other projects. So this is working as expected. However, when they are on the issue creation page/modal, in the project dropdown, they are able to see all other projects.
I've tried fixing this in the Permission scheme, if I remove the project role from the Browse Project permission, the user can't see anything, not even their own project. I've tried adding an Issue Security Level, but that doesn't seem to affect the project drown down list, only who can see the issue once it is created.
Any advice on where to go?
When a user selects "create issue", it should only offer the projects that they can create issues in.
You are very close to what you need to do, but you need to look at the permissions for "Create issue", not "Browse project" (although you'll probably need to consider it if you make changes - if, for example, they both say "Role: users", you will need to think about how to separate them)
If you spend enough time as a Jira admin - whether you are managing a single, mid-sized instance, a large enterprise one or juggling multiple instances at once - you will eventually find yourself in ...
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot