Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Next challenges

Recent achievements

  • Global
  • Personal

Recognition

  • Give kudos
  • Received
  • Given

Leaderboard

  • Global

Trophy case

Kudos (beta program)

Kudos logo

You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.

View group

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Creating issue shows all projects

I'm running JIRA over the cloud with different end clients having their own projects for issue management.  Currently I've got users assigned to groups and then the groups assigned to project roles.  When a project is created, I am using a project template that is tied to the project roles.

 

So what is happening...

When an end client clicks on the project listing, they can only see their project.  Entering in another project they don't have access to doesn't show up in the autocomplete and as far as they know, there are no other projects.  So this is working as expected.  However, when they are on the issue creation page/modal, in the project dropdown, they are able to see all other projects.

 

I've tried fixing this in the Permission scheme, if I remove the project role from the Browse Project permission, the user can't see anything, not even their own project.  I've tried adding an Issue Security Level, but that doesn't seem to affect the project drown down list, only who can see the issue once it is created.

 

Any advice on where to go?

2 answers

0 votes

When a user selects "create issue", it should only offer the projects that they can create issues in. 

You are very close to what you need to do, but you need to look at the permissions for "Create issue", not "Browse project" (although you'll probably need to consider it if you make changes - if, for example, they both say "Role: users", you will need to think about how to separate them)

Is there a solution for this? Jira makes it very hard to work with external clients this way.

Yes, take away the "create issue" rights in the projects you don't want them to create issues in.

Check, that works, Thanks nic!

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Jira

Announcing the waitlist for Jira Work Management

Hey there Cloud Community members! We’re excited to give you the first glimpse of the new home for business teams on Jira — Jira Work Management. Jira Work Management is the next generation of J...

141 views 3 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you