User limit access to making board updates

Question

I want to create a group of users who can look at the boards, and see status, but not have access to make any changes to the board. Reason is, there are a lot of managers who want access but I don't want them messing around accidentally and moving tasks. I created a Browse group, and added a user to it. This isn't working as I'd like as they can't access anything . There's access to Product and Product Admin as accessible 'switches'. If they are both non-selected, user can't get it. If Access to Product is selected, they can move statuses in a task. Is there a middle ground?

Thanks

Debbie Leskowitz · Answer

Thank you! When I created a new Role (Browser), I was informed that:

NOTE: When a new project is created, it will be assigned these 'default members' for the 'Browser' project role. Note that 'default members' apply only when a project is created. Changing the 'default members' for a project role will not affect role membership for existing projects.

I already have a project set up, and have entered several tasks, and set up a workflow. I really don't want to have to start over. Is there some existing Jira out-of-the-box role I could use?

Thank you,

Debbie

Dave Theodore [Coyote Creek Consulting] · Answer

This is easily done with Jira's flexible permissions. You will need to be a jira-administrator to make the changes or work with your Jira admin to get things set up the way you want them. If your Agile Board has issues from multiple Projects in Jira, this becomes a bit more messy, but I'll assume your board only has issues for one project in it.

The best practice is to use a Project Role in order to grant the "view only" access. You would either make use of an existing Role or create a new one, then grant "Browse Projects" permission to this Role.  As a Project Administrator, you can then add users and groups to this Role in order to give them read access to the issues and board.  For the users that need to be able to do normal development work, you would grant them more permissions in order to let them do what they need to.  It might be worthwhile to allow the "view only" users to do more than just view, though.  I'd expect they will at least want to comment on issues, but they may also want to be able to link issues to those in the project,  and maybe add attachments.