You are on page 1of 5

BOARDS AND PROJECTS

Board and project relationships

When a project is created, you have the option to create Kanban or Scrum board for the project,
creating simple one-to-one relationship between project and its board.

But other types of relationships between project and boards are also possible. A single project can have
multiple boards. For example, it may make sense to create individual boards for each team that only
displays the issues they are working on. It's also possible to have a single board tat displays issues for
multiple projects. For example, you may want to create a master board to display issues from multiple
related projects, or from multiple teams.

Board filters

A board's filter query determines what project and issues are displayed on the board. In its most basic
form, a Jira board is simply a visual representation of a query result. So a board is only limited by what's
allowable in JQL. A board's filter query result is accessed under Board settings→General.
Multiple projects on a board

BUSINESS REQUIREMENT→ This requirement calls for a board that displays issues from multiple
projects. It should also be made clear on the board, what issues belong to what project.

SOLUTION→ A board can be associated with multiple projects by creating a new board from an existing
project or modifying an existing board's filter query.

 Configuring a new board:

One way to associate multiple projects with a board is to create a new board, selecting the option to
create a board from an existing project. Then in the project field specify multiple projects. Note that
even though the board will query multiple projects, it still has a home project, as indicated by the
location field. This simply means the board will be gruped together with other boards from the indicated
project, but this does not determine what the board can display.

In the above example, even though the board's location is project B, the board is not required to display
issues from project B.

 Modifying an existing board:

Instead of creating a new board, you can modify the filter query of an existing board to incude multiple
projects. You need to be the board administrator to modify the filter query. If you are not the owner of
the filter, you won't be able to edit it directly. Instead, inspect the filter and clone it using save as, then
change the board filter to the newly saved filter.
 Column mapping:

If the project's included in the new multi-project board have different workflows, the statuses from
those projects may be remapped to different columns on the new board. To ensure issues and statuses
are displayed correctly, you can create additional columns on the new board and rearrange statuses as
needed. This won't affect the source projects.

 Organize the board by project:

To keep the board better organized, you can configure swimlanes by project. So each project's isses
appear in their own swimlane, making it easy to distinguish issues from the different projects.

Scrum and Kanban together

What if you have a Kanban project and you want to run some sprints for the project on a Scrum board or
vice versa? You have a Scrum project, but want to track some ongoing project tasks that aren't tied to
specific deadlines on a Kanban board? Or what if you started a Kanban project, but down the road,
realize you now need the project to be a Scrum project instead? How can we add different types of
boards to a single project?

Any number of boards can reference a single project. In the most general sense, a project can simply be
thought of as a collection of tasks or issues. And a board is just one particular view of those tasks and
issues. Since a project is just a collection of issues and a board is simply view of those issues, the project
itself is neither a Kanban nor a Scrum project. It's simply a Jira project. You can choose to view the work
in that project, either through the lens of a Kanban board or a Scrum board.
When you first create a project you're asked to identify it as a Kanban or Scrum project, but what youre
really doing is determining if the initial board for the project is a Kanban or a Scrum board.

Multi-board considerations

When adding a Kanban board to a Scrum project, you may need to change the project's workflow so
work can progress in the same way on both boards. For example, if workflow conditions are tied to a
particular column and that column doesn't exist in one of the boards, tasks may not be able to advance.

Other factors that may affect each board differently are issue type schemes, different estimation
methods, different work in progress limits.

Other board creation methods

We've seen how boards are created with new projects and how new boards can reference existing
projects. New boards can also be based on an existing filter query or be a copy of an existing board. Any
user can create a board, but to share dashboards and filters with others, global permission is required.
However when you copy a board, this permission is not required.

Board based on an existing filter

To create a board based on an existing filter, you must already have access to a saved filter, either one
you own, or one that has been shared with you. If you don't already have a saved filter, simply define a
new filter and save it. It will appear on the list of saved filters when you choose to create a board from a
saved filter, and you can choose it as the source of the new board.

Copy an existing board

When you copy an existing board, you become the owner of the new board, but not necessarily owner
of the filter. You will not be able to edit the filter, but you can switch to another filter. The board you’ve
copied is automatically shared with the users of the original board. The shared dashboards and filters,
global permission is not required.

To copy a board, view all boards and select copy from the ellipsis menu for the desired board.
KEY TAKEAWAYS

 A board is simply one view of a project's issues and work


 Create and configure boards in ways that serve the needs of your team and projects
 Don't let boards constrain how you setup your projects

You might also like