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?
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.
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!
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.
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!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot