Hi,

we are thinking of using JIRA for our project. We want to distinguish between users who should be able to view and submit bug reports, and developers who additionally should be able to create backlog entries and to do the planning. However, we do not want that all users can see our planning. Is that possible with Jira?

Thanks

Karl

 

 

3 answers

0 votes

JIRA permissions will let you do most of that - you can separate people out into sets that can view and/or edit and/or submit  and/or transition, and/or etc etc etc.

What you can't do is "hide planning".  If a user can see an issue, that's it, they can see everything based on that issue, inclluding any planning you might be doing.

Unless you decide to use JIRA Service Desk - that hides most of JIRA from the end-users - they can create really simple (or complex if you need it) requests, but then they don't get to see what happens in JIRA behind the scenes.

Thanks a lot for the quick reply. You mentioned that if users can see an issue, they can see everything behind it. That would be fine, provided that developers can mark certain issues as not visible to users. Is that possible?

Yes. You can set "issue level security" - it's a bit more complex and flexible than how I'm about to describe it, but you can do it. Essentially, you let people see the project and all the issues in the project. Then you set a "security level" on any issues you want to hide. As far as your unprivileged users can tell, a secured issue simply doesn't exist - it can't be searched for, it won't be counted in reports, and they can't get to it even if they know its ID!

0 votes
Joe Pitt Community Champion Sep 18, 2014

Be careful giving the jira-users group or 'everyone' access in a permission scheme. It will probably come back to cause problems. The jira-users group, by default, is where every user is put who has logon rights to JIRA.

0 votes

Very true, you need to watch out for the defaults - it is good that Atlassian have a default group for "everyone who can log in", but it's a nightmare that they also use it for "can access project" by default. It's well worth unpicking that as soon as you start using Jira, if you ever have any intention of limiting access to projects.

Suggest an answer

Log in or Join to answer
Community showcase
Sarah Schuster
Posted Jan 29, 2018 in Jira

What are common themes you've seen across successful & failed Jira Software implementations?

Hey everyone! My name is Sarah Schuster, and I'm a Customer Success Manager in Atlassian specializing in Jira Software Cloud. Over the next few weeks I will be posting discussion topics (8 total) to ...

3,149 views 13 19
Join discussion

Atlassian User Groups

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

Find a group

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

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you
Atlassian Team Tour

Join us on the Team Tour

We're bringing product updates and pro tips on teamwork to ten cities around the world.

Save your spot