Blocking issues transitions in a specific board, not the project

[David Vermeir]

Hi, 

I have an use case for creating (Kanban) boards that allow you to get an overview of the status of issues across different projects, but don't allow you to create, update, delete or transition an issue from that specific board.

Basically, I want to create boards that serve as a dashboard for all the work of my team across projects, but keep the actually interaction with the issues limited to the specific projects. 

Caveat: the viewers of this board can be users that actually have create and move issues permissions in the underlying projects, but they should not be able to do this in the overview board.

A more concrete example would look like this:

• Overview project (noone has permissions to create issues in this project, everyon can view)
  • Overview board (shows all issues of other projects (A, B, ...) but shouldn't allow updating or transitioning of issues from this board)
• Project A (everyone should be able to create, update, transition issues)
• Project B  (everyone should be able to create, update, transition issues)
• ...

I've create a custom permission scheme for the Jira project that holds the "overview board" that disallows all the issue permissions (besides viewing them of course) but this only seems to affect issues linked to that Jira project and not the others.

Is this even possible? If not, what are the alternatives to get a similar result.

[Walter Buggenhout · Accepted solution]

Hi @David Vermeir,

Transitions are part of the workflows. Permissions as to who can execute a transition or not are defined:

• at project level, based on the transition issues permissions defined there;
• through conditions in the workflow

Your board does not impact that in any way. It just helps you create a visual overview on the issues and adds certain additional capabilities (planning sprints, viewing reports, combining data from multiple projects ...).