nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Board Sharing

unknown

Hello All,

I need to set up one board where the Project Managers can add all the requirements from the client to the product backlog. After it is added, the tasks must be going to respective boards (backend team and frontend team) depending on the assignees to which team they belong to.

Backend and Frontend must be able to run their own sprints and the project managers on the main board must be able to sprints running on both boards on the main board like a consolidated board. But, the project managers must not be able to complete the sprint. It should be from the respective team only.

Can the access be given on boards as to who can close the sprint?

Accepted answers

All comments

John Funk

Hi Ganesh,

You can share the board filter with whomever you want and thereby, restrict it.

Trudy P Claspill

Hello @[deleted]

You could

1. Set up one project in which issues are entered for the Frontend and Backend teams.

2. Give the Project Managers access to create issues (also possibly Edit issue, Comment on issues, and Assign issues) but not Manage Sprints.

3. Give the members of your Frontend and Backend teams access to create, edit, comment, work on, assign, assignable user, schedule issues and Manage Sprints.

4. Create three filters:

a. one filter for all issues in the project - share this with the Project Managers, and optionally with the Frontend and Backend teams

b. one filter for issues assigned to the Frontend team members - share this with the Frontend team

c. one filter for issues assigned to the Backend team members - share this with the Backend team

5. Create three scrum boards; one based on each filter.

Sprints show in any board where an issue within the board scope is in a sprint. So the Project Managers will see in the all-issues board any sprint created in the Frontend and Backend team boards where an issues from the project has been assigned to the sprint. The PMs won't see the empty sprints. Without the Manage Sprint permission they will not be able to Complete any sprint.

The ability to Manage Sprints is a Project permission, not a permission specific to the board. To keep PMs from completing the sprints you simply don't give them the Manage sprint permission in the project. If you have both teams working from the same project they could potentially complete sprints in the other team's board. If you need to prevent that, then you would have to set up a separate project for each team, And then for the PMs you would need to create a filter that encompasses both projects and create a scrum board from that saved filter.

unknown

Should I make all three boards Company Managed?

unknown

@Trudy P Claspill can you please tell what filters I must have.

unknown

Hi @John Funk

I have created a Main Board names Development Board (Company Managed). Here all the backlogs are added.

I have created 2 Company Managed boards and Backend Team 1 and Front End Team and enabled filters.

Backend 1 ->

<strong>project = "Backend Team 1" or (project = "Development Board" and assignee in membersOf("backend 1"))</strong>

Front End Team ->

<strong>project = "Front End Team" or (project = "Development Board" and assignee in membersOf("Front End Team"))<br><br></strong>Now, whatever the issues are entered on Development Board and assigned they are appearing on Backend and Frontend boards respective. Although, I don't see subtasks appearing on respective boards until they are run on sprints. Now, how to make that

sure that the sprint cant be run on main boards but the PM sitting on the main board can have access to see consolidated boards.

Trudy P Claspill

Should I make all three boards Company Managed?

Boards are not Company Managed. That is a Type of Project.

Issues are contained in Projects. Boards are just a way to visualize and manipulate the issue. Boards select issues based on a filter. That filter can include issues from 1..n boards based on the criteria you choose.

I prefer Company Managed projects to Team Managed projects personally.

If you make Team Managed projects, such a project gets only one board linked directly to it and that is for all the issues in the board.

If you make additional boards based on Saved Filters, those boards can't be linked directly to the project. And the boards and their reports will not work quite the same as the native Team Managed board.

can you please tell what filters I must have.

That depends on a few factors.

Are you going to have the teams work in one project, or a project for each team? Looking at your response to John Funk it seems like you created three projects. You should not need three. The PMs will not not need a separate Project if they are just entering and viewing work that should all be owned by the Backend and Frontend teams.

If one project, exactly what method will you use to assign the issues to their respective team? Will you use the native Team functionality. Looking at your response to John it appears that you decided to use the User Group and membersOf() functionality. Only the issues from the Development Project that are explicitly assigned to the group members will appear in their respective boards. If the subtasks are not assigned, they will not be visible in the boards.

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

cloud

jira-software

jira-cloud

new-to-jsm

new-to-jira

atlassian