Working with the Board

Introduction

When working with the Board, it will only allow you to move around tasks that are editable in Jira and when the tasks are assigned to a Box with a status different than Done. So, if a task's Jira status is set to DONE, you might not be able to move it, and the app will tell you why. This applies to both cards assigned to Boxes and those in the backlog sidebar.

Basic operations on tasks include:

  • Planning

  • Bulk re-planning

  • Adding tasks to the scope

  • Creating dependencies

  • Create task-based objectives

You can perform the above actions using drag and drop (except for adding tasks to the scope). Once you select the tasks and start dragging them, all the Timebox areas where you can drop them will be highlighted. Read more about working with tasks in Multi-select

Planning

Timeboxes define consecutive timeframes used for work planning. It helps to think of them as, e.g., sprints, iterations, increments, or stages.

You can add tasks to Timeboxes (e.g., Program Increment, Iteration, Stage, etc.) by a simple drag-and-drop action. All you need to do is drag a task from the backlog and drop it in the Timebox you choose. You can freely move your tasks between Timeboxes and the backlog:

2024-02-27_11-03-30.mp4

If you synchronize your Board module with one of the task fields, you can also add your tasks to the Board by simply editing the synchronized field. Just make sure all the tasks you want to plan are in the Box's scope (Scope definition).

Here's an example: if you set up the Board in such a way that at the lower level each team uses their own Jira Agile Board and each Iteration is in sync with the sprint number, the team only needs to choose the right sprint in the Sprint field of a task card to automatically add this task to a Timebox assigned to this team at the upper level.

You can also create Timeboxes manually or create Timboxes from Jira Boards automatically.

Tasks with children

When you assign a task to a Box (for example, Program Increment), and it has children that are not assigned to any Program Increment, the parent task is still visible in the backlog, so the context of children is still visible:


Once all the children have been assigned, the parent task is no longer visible in the backlog (unless you have selected the 'Show already planned tasks' option):

Bulk re-planning

You can streamline your work by selecting multiple tasks and moving them between Timeboxes and the backlog. To select multiple tasks, press and hold the Command key on a Mac or Control key on Windows, then click the tasks. To select multiple tasks listed together, click the first task, press and hold the shift key, and click the last task. All tasks in between are included in the selection.

Use CTRL+left click on Windows or CMD+click on a Mac to select multiple tasks.

Add tasks to the scope

Another way of adding your tasks is by clicking the "+" button at the bottom of every Timebox. This way you will change the Box's scope.

When you add a task to the scope, the following task fields will be updated:

  • Box field

  • Team field

  • Parent Box field (if available and synchronized)

Create dependencies

To create dependencies between tasks:

Method 1:

Click and drag → click on a grey dot and drag an arrow to a card to create a dependency.

 

Method 2:

Click on the grey circle → a pop-up appears. Fill in the fields to create a dependency. 

The task you have clicked on is automatically selected as a source task. 

Note: To use this feature, make sure the Expand dependencies option has been selected:

Create task-based objectives

You can create task-based objectives directly in the Board module.

  1. Find a task (Jira issue/basic task).

  2. Right-click on a task and select Create objective based on this task.

A new objective is immediately visible in the Objectives module.

Basic operations and outcomes

The table below shows several basic operations regarding task updates in Jira.

Operation

Condition

Outcome

Operation

Condition

Outcome

Updating the task information

  • Unspecified Timebox synchronization field

Task outside the scope of the Board module

  • Specified Timebox synchronization field

  • Unassigned team

Task visible in the sidebar Backlog and in the Timebox backlog swimlane.

  • Specified PI or Iteration Timebox field

  • Assigned team

Task visible in the Team's swimlane.