skrümGitHubGet started

Planning poker

Tasks and imports

Add the tasks to estimate, by hand or from Jira, Linear or GitHub, and put them in order.

This page shows how to fill the queue of a game with tasks typed by hand or imported from your tracker. Everyone in the game except guests may add tasks; importing is also closed to observers of the team. Only the facilitator orders the tasks, picks the one to estimate and deletes them.

Add tasks by hand

The Tasks panel is on the right of the room; Hide tasks in the header closes it.

  • For a title alone, type it in Add a task… and select Add.
  • For a title and a description, select Add task. The description accepts Markdown. A section under an “Acceptance criteria” heading is shown apart, beside the description.

The task description is collapsed by default. Select Description to expand it; the table moves down to make room for the full text. Select it again to collapse it.

A title has 200 characters at most, and a game holds 200 tasks at most. To change a task typed by hand, select Edit task, the pencil on the task at the top of the room.

The task queue of a game: two estimated tasks, the task being voted, a task to come, and the buttons to add and import

Order the queue and pick a task

As the facilitator:

  1. Drag a task by its handle to move it. With the keyboard, focus the handle, press Space, move with the arrow keys and press Space again.
  2. Select a task to estimate it. Its first round opens for everyone.
  3. Select Delete task, the bin on the task at the top of the room, to remove it with its rounds and votes.

Picking another task discards nothing: a round left open keeps its hidden votes and resumes when you come back to its task.

Each row shows the number of votes of the task’s last round, and its estimate once saved. On a deck of numbers the panel adds up the estimates, as in “8 pts estimated”.

Import from a tracker

The team needs a connection to Jira Cloud, Jira Data Center, Linear or GitHub.

  1. Select Import under the queue.

  2. If the team has several trackers, choose the Source. Issues load automatically. Leave the filters empty to browse all issues accessible through that connection.

  3. Narrow the list with optional filters:

    Tracker Optional filters Query
    Jira Cloud and Data Center Project, a Scrum or Kanban Board, and an active or upcoming Sprint on Scrum boards A JQL query
    Linear Team and an active or upcoming Cycle A search
    GitHub Repository and an open Milestone A search
  4. Use Search issues and the status filter to find tasks. These controls work with every tracker. All statuses removes the status restriction.

  5. Scroll to load more pages, or select Load more. The list is not limited to the first 100 issues. Tick or untick issues as you browse; issues already in the game cannot be imported again.

  6. Select the button that counts the issues you ticked, for example Import 3 tasks. You can select at most 100 issues per import, within the game’s remaining capacity.

An empty filter adds no restriction. For example, selecting a Linear team without a cycle includes its issues with and without a cycle; leaving the team empty includes issues across the connected workspace. The same applies to Jira projects, boards and sprints, and GitHub repositories and milestones. Clear a filter to broaden the list again.

In Jira, Project limits issues to that project. Board applies the board’s saved filter, which can cover several projects. You can choose a project independently of a board; when both are selected, issues must match both.

An example of importing Jira sprint issues, including issues already imported

The same picker is in the New session dialog, under Tasks, on the Import tab. Choose the source there if the team has several connected trackers.

What an imported task keeps

An imported task shows the key of its issue, which opens the issue in the tracker, and its type, labels, assignee, status and the estimate it has there. Guests see the key, the type and the labels only.

Its title and description are managed in the tracker and cannot be edited in Skrüm. To fetch them again, open More task actions, the … button at the top of the queue, and select the refresh action, for example Refresh from Jira. An issue the tracker no longer returns is marked as not found and keeps what it had. A refresh never changes an estimate saved in the game.