Real-time voting

Everyone on the team votes on a story at the same time and the cards flip together.

The facilitator opens an issue for voting and each player picks a card. Votes stay hidden until the reveal.

All cards flip at once, so nobody anchors on a teammate's number.

A countdown runs before the reveal, and the table can flip automatically once every player has voted.

What is planning poker?

Async voting

Team members vote on issues at any time, without being in the session together.

Votes are stored per issue, so one person estimates on Monday and a teammate estimates the same issues on Tuesday.

The facilitator reveals one issue at a time, or reveals every issue that has async votes in a single action.

Async and live voting run on the same board. A remote team can estimate async and keep the live call for the issues people disagree on.

Planning poker for remote teams

Card decks: Fibonacci, T-shirt sizes and more

Five decks are built in and cover the common story point and sizing scales.

Fibonacci (0, 1, 2, 3, 5, 8, 13, 21, 34, 55, 89), modified Fibonacci (0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100), powers of two (0, 1, 2, 4, 8, 16, 32, 64), T-shirt sizes (XS to XL), and original estimate in hours, days and weeks.

Every deck includes a question mark card for an unknown estimate and a coffee card for a break.

The deck is set per game, so one team estimates in story points while another uses T-shirt sizes.

Custom card decks

Teams create their own card values and reuse them across games.

A custom deck holds any set of values, numeric or text.

Saved decks appear in the deck picker and can be edited or deleted later.

Reveal countdown and auto reveal

The table controls when the cards flip.

A countdown gives late voters a moment before the reveal.

Auto reveal flips the cards as soon as every player has voted, so the facilitator does not have to.

Both are per-game settings and either can be turned off.

Results, average and agreement

After the reveal the table shows the vote spread, the average and an agreement score.

Each card value shows how many people picked it and who they were.

The average is calculated from numeric cards only. It can be hidden per game when a team does not want it to anchor the discussion.

Agreement is shown as a percentage with a chart, and unanimous rounds trigger confetti.

Voting history and export

The web app keeps every voting round of a game and lets you go back through them.

Rounds are grouped by meeting and show the issue, the result, the average and the most voted card.

History can be exported so a team keeps a record outside the app.

The Jira plugin stores results per issue but has no game-level history browser.

Discussion timer

A shared timer keeps discussion on each story to a fixed length.

The facilitator starts, pauses and resets it, and adds time mid-discussion.

The default is 45 minutes and the duration is editable in place.

It restarts automatically for each issue when that option is on, and plays a sound when it runs out.

Spectator mode

A participant joins and watches without voting.

Spectators are left out of the vote count, the average and the agreement score.

This suits product owners, stakeholders and anyone attending sprint planning who should not influence the estimate.

Import Jira issues by board, sprint or JQL

The Jira plugin pulls issues straight from Jira into the estimation session.

Pickers filter by project, board, sprint, epic, issue type, status and saved filter.

A JQL mode with autocomplete covers anything the pickers do not.

Issues arrive with their summary, description and current estimate, and open in the Jira issue modal from inside the session.

Planning poker for Jira

Story point write-back to Jira

The agreed estimate is written back to the Jira issue when the round is revealed.

Each issue shows its sync state: syncing, synced, not synced, or error.

After a re-vote the plugin offers to clear the story points field in Jira and remembers the choice.

Writes that fail can be retried in bulk.

Estimation field selection

The plugin works out which Jira field holds the estimate, including renamed and custom fields.

Auto mode checks the game setting, then the user preference, then the board estimation statistic, then matches the field by name.

The field can also be pinned by hand for a game.

After a write the session names the field it actually updated, so there is nothing to guess.

Games dashboard

The plugin lists every estimation game in the Jira site in one table.

Columns cover name, creator, created date, last joined and last activity, and the table sorts on any of them.

Games are filtered by creator and deleted from the list.

Which columns are visible is a per-user setting.

The web app has a personal list of your own recent and created games instead of a shared table.

Facilitator roles and permissions

Each game controls who can reveal cards and edit issues.

Permission is set per game and is either everyone or a named list of people.

In the web app the game can also be handed to a different facilitator without recreating it.

Multiple facilitators

More than one person can create and run games for the same team.

In the web app a paid plan covers a number of facilitator seats. A facilitator is someone who creates paid games, usually a scrum master. Seats are invited by email and can be removed and reassigned at any time.

The Jira plugin is licensed per Jira site rather than per seat, so anyone who can open the plugin can create and run games.

Players invited to a game never need a seat and always play for free.

Invite players by link or QR code

A game has one permanent URL that players join from.

The link is copied from the session or shown as a QR code for people in the room.

The URL does not change, so a team reuses the same game for every sprint planning session.

Join without an account

Players join a web session with a display name and no sign-up.

Only the person creating the game needs an account, which is created with Google, Microsoft or an email address.

Inside Jira there is no separate account at all. The plugin uses the Jira identity of whoever opens it.

AI estimation

In development. Expected Q4 2026.

This section is a placeholder so that links pointing at it today keep working. It will be rewritten with the details when the feature ships.

Jira integration

Jira works through the plugin on the Atlassian Marketplace, not through the web app.

The plugin runs inside Jira Cloud and covers issue import, estimation and story point write-back.

The web app does not connect to Jira. Jira import was removed from the web version.

For Jira Server and Data Center, export the issues to CSV and import that file into the web app.

Planning poker for Jira

Linear integration

The web app connects to Linear, imports issues and writes estimates back.

The connection is made once with OAuth from the account settings.

Issues are searched with the same filters Linear uses, then imported into the session.

On write-back, T-shirt sizes map to the 1 to 5 estimate scale Linear uses.

CSV import and export

Issues are imported from a CSV file and results are exported to one.

CSV import is the route for any tracker without a direct integration, including Jira Server and Data Center.

The export covers summary, key, description, link and estimate.

Both are in the web app only.

Import issues from URLs

A list of issue URLs is pasted in and becomes issues in one step.

Each URL becomes an issue in the session with a link back to the original.

This suits trackers that have no integration and no convenient CSV export.