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; } } }

Users seeing all projects when creating issues

Jim Hackney

When my users create an issue, the Project drop down menu on the Create Issue page shows all projects instead of just the projects they are assigned to. I want to change this behavior so that the only option they have is/are their project(s).

I have created group roles using the following template:

AgencyName-ProjectName-Admin

AgencyName-ProjectName-Developers, etc., etc.

I have added the users to the appropriate groups and assigned the groups to the appropriate group roles. I then created a custom Permissions Scheme and added the groups to the scheme in the appropriate places.

The groups have been added to global permissions.

I am unsure of what else to do. When doing a search I found one answer to this question from 2012 but the directions in the answer didn't match my screens so I assume that things have changed a lot since 2012.

Accepted answers

All comments

Nic Brough -Adaptavist-

Look closely at the "create" permission in the scheme for the projects. The users are getting the projects in the drop down for all projects that they could create issues in.

Generally, you want to avoid using groups in schemes, your description seems to be that you're granting permissions twice and that's a bit of overkill. Let's say you have roles of Users, Developers and Admins. Grant all those roles "Create", but don't put the groups in the permission scheme. Just add the group to the project role when you need that group to create issues in that project.

Jim Hackney

Thank you for your help. Sorry for the delay in answering. I work for a state and JIRA is used by different agencies in the the state, each with their own JIRA admin under a centralized JIRA System admin group. The way they want us to handle roles and permissions is to create groups, add users to the groups (both via AD), and add those groups to the various roles. Then in the permission scheme, add both the project roles and the group roles. I agree that it seems like duplicating work but that's what they want.

Are you saying that if the JIRA admins in these other agencies do not lock down their projects then my users are going to see their projects and there's nothing I can do about it or am I misunderstanding?

Nic Brough -Adaptavist-

Yes, that's correct, if your admins are demanding to do things that way, they're wrong, and you can't do what you need to.

Frankly, they need to stop being silly and stop using groups in permission schemes. It's not the only solution to your problem, but it is the best, and none of the others are going to work until they stop it either.

Jim Hackney

So, just to make sure I understand (I'm going to address the issue), the proper way would be to create the groups and users in AD as we have been doing, add the users to the groups we want them to be in, then add those groups in the roles we want them in. In the Permission screen we just need to use the project roles and NOT the custom groups because we are just duplicating the process.

Also, as a test, yesterday I removed all of the custom groups from the permission scheme (kept them in the roles) but it didn't make a difference. User can still see everyone's projects. The groups I have them in are unique and are not used by any other project. It seems illogical to be affected like this by the actions of JIRA admins in other agencies.

Neha Singh_9mip8x

See the permission scheme for the other projects the clients are able to see.

In that for creating an issue- remove any logged in user option and change into jira_user group and make sure that the clients are not in that group.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-core