Do multiple scrum and kanban boards support the same issue filter?

Question

I'm working in a new team/board/filters/sprints.

I know I need to be careful with board RANKING getting updated across boards, but will I break/change anything if I:

- Have multiple boards with different columns and mapping?

I need to trial and error a few things as I setup the board and don't want to break anyone's experience

Trudy P Claspill · Answer

Do you need to actually manage/manipulate these issues, or are you just wanting to visualize the issues across multiple projects?

If you just want to see the issues, it should not be a problem to set up a board that uses a filter that pulls the issues from multiple projects. I would recommend that you not try to manipulate the issues in that board though. Any changes you make to the issues themselves will be reflected in all the boards.

The mapping of statuses to columns also will not matter. That is a board configuration and by itself does no affect the issues. The issues are affected when you move them between columns or within a column, as that changes the status and/or ranking of the issue, which will reflect in all the boards that show the issues.

It also won't matter what the workflow of the original issues is. The board does not dictate the workflow for an issue. That is in the Project Settings of the project where the issue exists.

If the team boards are using sprints, you will see all the teams' sprints in your board if you set it up as a scrum board. Don't make changes to those sprints in your board because those changes will reflect in the original boards. If you create sprints in your own board and add issues to them, that will also be reflected in the original boards. If you create a Kanban board, you won't see the teams' sprints.

In the Reports section of your board you will be able to see reports that span the teams for all the issues you include in your board.

Are the projects Company Managed or Team Managed? If the projects are Team Managed, they are architected a bit differently. A board you create manually will not manage/show issues from a Team Managed board the same way it manages/shows issues from a Company Managed project. That could cause you confusion.

Bea Tea · Answer

@Trudy P Claspill Thanks for the welcome and great reply! I will be careful moving across columns if it DOES change the state in the ticket.

I'm looking into a single board that can track against multiple teams (different Jira projects) connected to the same initiative.  I noticed some ticket types have different workflow though... Any tips on managing a board against multiple projects would be appreciated!

Trudy P Claspill · Answer

Hello @Bea Tea

Welcome to the community.

Boards are a way to visualize and manipulate issues that exist in projects.

You can have boards that show the same issues and have those boards have different column/status mappings. Moving issues between those columns will change the status of the moved issues. That will be reflected in all boards where the issues display.

If you have multiple scrum boards that reference the same issues, sprints in each of those boards may appear in other boards.

If you need to experiment with things I would strongly encourage you to use test projects and test issues rather than working with live data.