Project level access in JIRA

[Stanly Thomas]

I'm a newbie to the JIRA administration. I have few questions related to project access level.

Our company wants to set up JIRA users to an individual project level access rather than having access to all projects. What is the easiest way to do this setup? 

Is there a way users inside a project can view only to the issues they've raised.

[Thomas Schlegel · Accepted solution]

Hi Stanly,

you should create a permission scheme and grant the different project permissions to project roles.

E.g. grant "Browse projects" to project role "Developers".

Then, add your users to the project roles within the projects, they are allowed to see (Users and Roles in the project administration).

After that, assign the new permission scheme to your projects. As a result, only users added to the project role "Developers" have the permission to watch the project.

You can also set the "Browse project " permission to "Reporter" - by that, the issue should be invisible to any other user except the reporter. But I wouldn't do anything like that. This may result in issues that are assigned to a user who is not able to see the issue, gets no notification etc. 

[Nic Brough -Adaptavist-]

Look at the permission scheme - this is a set of rules about who can do what.  Combine that with a look at the users in the project.

A common problem is that the defaults for Jira are "access for anyone who can log in", and that's not helpful for a lot of us.  What you need to do is look at the permission scheme to see who has "browse project".  You'll usually find this says "Role: Users".  That's fine itself, the problem is that the default membership of Users in all projects is a group that contains everyone who can log in.

You need to remove that group from the role in every project (I'd strongly recommend going to Admin -> Roles and removing it from the default as well).  As you remove it from each project, you will need to add back people (and/or groups) who should retain their access to the project.

Once you've done that, you'll find you can manage the project access separately.