Multiple boards, backlogs, tickets under same project

Adrian Munteanu

Hey folks,

Need your help to understand if what I am after is possible:

Current: as a product owner, I own multiple products, for which I am running separate sprints, with their own cards, where I can give my developers permissions to view and edit the cards.

Desired: I want to have under the same structure (let's say a project named after the area I am leading), under which I want to have all my products' boards, with their issue type names, separated on different backlogs specific for every product and accessible only by the assigned developers. Tried with classic project and so far was able to accomplish the followings:

created a project called TOM, under which I have been able to create following different boards: KLARA, CBS, Shotgun, WebApps. Related to these boards, I have also created various Story types for every of these products/boards. The first problem I have is that all cards inherited the Project name and they're all named like TOM-xx. Could that be customized?

Also, checking the backlog for various boards I have created under TOM project, all cards are showing, regardless of the board I am choosing. How can I see them on separate backlogs, related to the boards I am choosing?

Also, presuming that above would be possible, how can I separate accesses of developers per boards?

Thanks,

Adrian

 

Trudy P Claspill

Hello @Adrian Munteanu 

Welcome to the community.

First, let me clear up a concept.

Issues exist in projects, not in boards. Projects are the containers for issues. Boards are just a way to visualize and manage the issues. You do not create issues in a "board"; you create issues in a project and the board is configured to view issues in 1..n projects.

You cannot customize the ID assigned to issues - the XYZ-123 identifier. This is going to pick up the key for the project in which the issue exists, always.

You can create boards that show a subset of the issues in the project by customizing the filter used by the board. You would need to have something in the each issue to identify which board it should display in, like a unique Component or Labels value, or you may choose to have a totally separate custom field for that. Then you would modify your board filters to include a criteria for that field/value. Note you would want to include also the criteria for the field being empty, so that the card would show up on all boards until it is properly tagged;

example:

project=TOM and (Component="CBS" or Component is empty)

Separating the access for developers to be able to view and modify the cards only for their "board" is more challenging. Permissions are generally set at the Project level. While you can limit who can view your board by limiting with whom you share the Filter used by the board, the developers would still require View and Edit permissions in the underlying project where the issues exist. And allowing them to view and edit only a subset of those issues would be very challenging to implement.

If you truly need your developers locked out of the boards for other products, then you should separate the issues into Projects based on the products, and boards per project.