...
In this case, the screenshot shows a board to plan releases (a.k.a. fix versions), where there is a matrix Priority by Components. So, the team can balance the issues to be release in the upcoming versions based on the prority given, but also based on the specific components.
Priority by components
The release planning requires the selection of an existing project, and only one, before you can start planning your backlog.
Planning your Components
The next screenshot shows a board to plan components, where the backlog is a matrix Issue type by Sprints. Here, the team displays the issues that don't belong to any component, but are already in a sprint. In this situation, it's recommended to have all the issues organized.
The component planning
Issue type by priority or sprintsrequires the selection of an existing project, and only one, before you can start planning your backlog.
