Access to boards

Bakhodir December 11, 2021

At the moment we have 2 boards. The first board is created for the product owner who only keeps records of backlogs. The second board is attached to the first board. The second board is created for developers.

The problem is that developers should not have access to the first board (the product owner board). There is no ability to edit access to the boards in the JIRA settings.

How can this be solved?

 

1 answer

2 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 11, 2021

Welcome to the Community!

One of the board settings is "who this board is shared with", which will probably say "shared with project", so anyone who can see the project can see the board.  You can change that if you want, limiting it to maybe a group of Product owners.

I would strongly recommend that you do not do that.  The whole point of boards is clarity and working together.  Especially in Scrum where the product owner is supposed to be working directly with the developers to prioritise and rank the backlog.

Jack Brickey
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
December 11, 2021

Agree and the other point to make here is that just because they don’t have access to the board does it mean they will not have access to the underlying issues. So the only thing you would really be doing is hiding a visual representation of the issues from them. If you truly want to have a project management board and a development board then you really should consider separate projects. When issues on the project management board are ready for development or approved for development then they could actually be moved or linked to a new issue in the other project. Of course you could also consider different issue types within the same project and leverage issue level security. However you’re getting into a lot of complexity and is Nic says the whole idea is to have an open development world.

Suggest an answer

Log in or Sign up to answer