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

But why he sees all projects in the create project screen?

Roberto Soto Alvarez, MBA

I want to have a user to create an issue in only one project.

The user can see only one project in the projects list

But why he sees all projects in the create project screen

I created a group to hold the users I want to work on the project.

I tried to modify the permissions, Roles, fields, screens and issue types but I still get the list of all my projects on the Create Issue Screen. But still, I got the same list of all projects when creating an issue for this project.

Can you help?

browse projects.png create issue.png

Accepted answers

All comments

Andy Heinzer

Given the screenshots you have provided, it looks like this user has the correct Browse permission. Which appears to be set to that one project. However if they can see the other projects in the create issue screen, then this is likely because the user still has the permission to create issues in those other projects.

Without the browse permission they can't actually see the issues they create in those projects, but they can likely still create them.

Check out Managing project permissions. Specifically I would focus on the permission scheme in use by these other projects and then determine what role/group is granted access to the Create Issues permission. By default with Jira this tends to be 'Any logged in user' or something alike. If you change this for these other projects you can likely resolve this, however you need to make sure that you grant some other group/role access to create issue there, otherwise no one will be able to create new issues there.

You can also use the Jira permission helper to determine if this user is being granted access to create issues in these other projects by some unexpected group membership/role.

Roberto Soto Alvarez, MBA

Thanks a lot Andrew for your fast response. I'm going to take a look at the links you provided and come back later on.

Roberto Soto Alvarez, MBA

I went all over the permissions documentation and cannot make just to show only the authorized projects for a user. It shows all the projects. In fact there is a document mentioning that any user will see all projects while creating an issue . Too sad.

Andy Heinzer

Please let me know what documentation you are referring to.

I just walked through this process in my own test instance and I was able to create a custom permissions scheme that does not grant the Create Issue or Browse Issue permissions to the "Any logged in user" role.

Instead I set those permissions to only allow for the project role of Administrator. When I then assigned this permission scheme to my other project, my account that is not an admin in that project does not have the ability see that project at all, including in the issue create screen.

My Jira version I did this in was 7.7.0, but I believe this still is valid for many older versions of Jira as well.

Welcome!

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

Quick Links

Find more posts tagged with

jira-software

permission