• Community
  • Products
  • Jira
  • Questions
  • What permission scheme is needed to allow a user to see only one project and both view and create issues in that project?

What permission scheme is needed to allow a user to see only one project and both view and create issues in that project?

I am trying to set up a user that can see only a single project. I seem to have everything set up so that they can add issues, but they cannot see any of the issues in the project.

I tried adding the Browse Projects permission, but that now gives them the ability to see more than the single project. I've followed the instructions in various other questions, but I have not been able to set permissions/users up so that a user can both see issues and create issues in a single project.

3 answers

1 accepted

0 vote
Joe Wai Tye Atlassian Team Jun 13, 2014

Hey, just to expand a bit on what Nic mentioned, you probably want to check the Permission Schemes, and configure it such that the specific user only has 'Browse Project' permission for that particular project.

Some things that you wanna watch out for is the group memberships of that user, make sure he's not a group that allows him to view the issues in other projects.

0 vote

How are you allowing them to "browse projects"? What's the mechanism that gets them the permission - group, role, specific user id?

I assume you've unpicked the default "jira users group gets to see everything by default"?

It is the inclusion of the users group that causes all projects to show.

I have to agree withs ome of the previous questions on this topic that the user permissions scheme is unnecessarily complicated. I say that even though the application that I test has a very complex permissions scheme (which I also do not understand).

Actually, the permissions aren't any more complex than their power and flexibility need them to be. The main problem tends to be that the defaults you inherit when you first install Jira are terrible for systems that want to restrict people, and because it's not clear that they are awful up-front, they get reused or used as the templates everywhere, making them a nightmare to unpick.

Once you've got them separated out, permissions are quite simple - you can see "person X can do Y because their profile matches rule Z"

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published yesterday in Jira

Mission-critical battery manufacturer fulfills FAA software requirements with Commit Policy Plugin

EaglePicher Technologies is a leading manufacturer of battery systems for diverse industries like defense, aviation, space or medical. As they operate in highly regulated industries, keeping a clear ...

127 views 0 2
Read article

Atlassian User Groups

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!

Find my local user group

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

Groups near you