The plan mode allows you to plan your issues using a third dimension. This third dimension can be sprints, components or releases. We explain each one of those below.
This mode is presented in two parts, the backlog area (left part) and the planner area (right part). The issues flow from the backlog to the planner, simply by dragging them. When you need to unplan an issue from the planner, you don't need to remember where it belonged, just hover the appropriate issue and a "X" will appear. This "X" moves the issue to its original place.
Backlog
The backlog shows the issues that are not yet planned either in a sprint, component or release (depending on the third dimension selected in the planner). In this area, you can select up to two different dimensions (columns and rows), filter by JQL or using our quick filters, select saved boards, projects or filters, etc. The board functionality is explained with more detail in Getting Started with Canvas for JIRA, so read that page first if you are not yet familiar with it.
Planner
The planner shows a third dimension, different from the dimension(s) previously chosen in the backlog area. This means that you cannot select the same dimension as in the backlog e.g., if we have selected a board with priority by sprint, we won't be able to select the sprints dimension in the planner.
If you miss any of the three dimensions - sprints, releases or components - make sure that you have those selected in "Manage fields", within the Canvas administration.
Planning your Sprints
The following screenshot shows a board to plan sprints, where the backlog is filtered to work just with stories, in a matrix Story Points by Components. Thus, the team can easily plan based on the capacity and the targeted components for the upcoming sprints.
The sprint planning requires the selection of an existing agile board, before you can start planning your backlog. The planner shows the currently active and future sprints available.
For those users with the "Manage sprints" permission (check this page for further info), the planner will display buttons to create, edit, complete or delete sprints.
Planning your Releases
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.
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 requires the selection of an existing project, and only one, before you can start planning your backlog.
