Estimation meetings shouldn’t need a second tool, a shared screen, or someone copying numbers back into Jira afterwards. Starting today, planning poker is part of the app. Open your board, choose the Estimate button in the app’s top bar, and your team estimates stories and their parents together, live, right next to the backlog.

How a round works

1. Pick an issue. Choose Estimate next to any story or parent in the board’s backlog or future sprints. One round runs per board at a time, and everyone on the page sees it update live.
2. Vote in secret. Pick a card. Others see that you voted, not what you voted. Changed your mind? Pick another card.
3. Reveal together. See every vote, the range, the average and the most common card, or that everyone agreed.
4. Save to Jira. Save M to PROJ-12 writes the estimate to the issue. Not settled yet? Choose Vote again.

Stories and parents, side by side

Issues are grouped under their parents. A parent gets its own estimate, shown next to the sum of its listed children, so you can see at a glance whether the big picture and the detail agree.

A deck for every team

• Fibonacci: 0, 1, 2, 3, 5, 8, 13, 21
• Modified Fibonacci: 0, ½, 1, 2, 3, 5, 8, 13, 20, 40, 100
• T-shirt sizes: talk in sizes, save in points. You decide what each size is worth; the defaults are XS 1, S 2, M 3, L 5, XL 8, XXL 13.

Each board chooses its own deck on the estimation page, and anyone who can edit issues on the board can change it between rounds.

Built so nothing slips

• No lost results. Ending a session or moving to another issue before saving asks first: save and continue, continue without saving, or cancel.
• Open the issue without leaving. Click an issue key, or View or edit in the round, to open the full Jira issue on top of the page. Edit it, close it, and the list updates.
• Still Runs on Atlassian. Your estimates are written straight to Jira, and the advanced app keeps its Runs on Atlassian status.

Good to know

• Anyone who can edit issues on the board can run a round.
• Saving an estimate to the issue requires a board that estimates in story points. Boards that estimate by time or issue count can still vote.
• The board must be selected in the app’s configuration first.
• Available now: Backlog Refinement, Sprint & Capacity Planning for Jira 7.1.0 and Sprint Planning, Capacity and Resource Planning for Jira 2.22.0.

Read the full release notes for Backlog Refinement, Sprint & Capacity Planning for Jira and Sprint Planning, Capacity and Resource Planning for Jira, or get the apps on the Atlassian Marketplace: Backlog Refinement, Sprint & Capacity Planning · Sprint Planning, Capacity and Resource Planning.