nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Limit the list of projects when creating an issue

JVHE

I want to configure that a certain group of users has only access to specific projects (in jira cloud).

I've used following guide to accomplish this:

https://confluence.atlassian.com/jirakb/how-to-restrict-project-access-to-different-isolated-user-groups-290750862.html

After this the group of users can only browse their projects, which is ok.

However, when creating a new jira-issue, the user can still see all project in the listbox of available project. This is not wanted of course.

Could you please explain me how to restrict the listbox of projects ?

Accepted answers

All comments

Tinker Fadoua

Hi Joost,

If you remove the users access to the projects you don't want them to see, they will no longer be able to see them on the list of projects.

Browse permission will be the first one to check.

JVHE

I don't understand.

All my other projects have another security sheme in which is defined that only another usergroup may browse.

For example :

given :

usergroups : A and X
projects A1, A2, B, C, D

usergroup A may only have access to projects A1 and A2
usergroup X can have access to all projects

I've configured :

security schema "for usersgroup A" with browse-permission set to "usergroup A". I've associated this schema to projects A1 and A2
security schema "for all other users" with browse-permission set to "usergroup X". I've associated this schema to projects B, C and D.

When a user from group "usersgroup A" creates an issue, he still can see project B in the listbox of available projects.

I hope this helps to understand my problem.

Tinker Fadoua

Ok thank you for the details!

Issue Security applies to issues not to projects. Users can still see the projects on the list but shouldn't be able to browse issues inside the project.

JVHE

So could you please provide a step by step instruction on how to accomplish my needs?

Luke Brothers

Check all your permission schemes, looking at "Create Issues" and who/what that's granted to. Just now, in my own instance I found a few permission schemes giving access to any logged-in user, and others granting access to users with application access. Correcting those permissions -- even against schemes used by other projects -- did the trick. Now my users in one project may only create issues within one project.

unknown

Hi @Luke Brothers Do you mean you give access to "any logged-in" user? could you please further explain on the above how you did the trick to restrict user to create issues within one project (that he /she was not given access to), so that the user would not be able to create issues in the projects that they are not granted permission to. (though they are still able to see the list of projects in the project field). Thank you so much in advance.

Luke Brothers

Hi @[deleted]I don't believe I have users who can view other projects but only create issues in some specific projects. I needed to limit the projects users could see when creating issues. I accomplished this by opening all permission schemes and ensuring the "create issues" permission was accurate. I found that some permission schemes uses by other projects were giving all users permissions. So...even though these other permission schemes weren't used by my particular project they still allowed users access to other projects.