Team backlog estimation inside Jira Cloud — user guide, privacy policy and support.
← Documentation home · Support
In two places, both opening the same Games screen: Apps → Planning Poker in the Jira top navigation, and the Planning Poker tab inside a project. See Documentation home.
No. The app has no admin or project settings screen. You only need a Jira project with work items, and an estimation field the app is allowed to write to — see Jira configuration.
No. Games are global. Opening the app from a project tab only preselects that project in the Spaces filter; a single game’s backlog can hold work items from several projects.
Open the ⋯ menu of the game on the Games screen and choose Copy game URL, then share the link. Anyone who may see the game can also find it on the Games screen without a link.
Because you are not on the game’s estimator list. Only the facilitator and the people added as Estimators get the card deck; everyone else joins as a spectator. The facilitator can add you through Edit game → Edit game tab.
Yes. Pick another card and the results update for everyone straight away.
∞ means too large to estimate, ☕ means I need a break. They count as votes and appear in the distribution, but they have no numeric value, so choosing one as the final estimate keeps it in the game and the report without writing anything to Jira.
Two or more cards got the same number of votes, so there is no single answer. Discuss the difference — the notes people left with their votes usually explain it — and click Re-vote for a new round.
It appears from three votes onwards. With one or two votes there is no majority worth calling a result, so the room shows only the count, the distribution and the notes.
The votes are revealed automatically. The facilitator can also reveal them at any moment without waiting for the timer or for the last voter.
The app is built for a live round: everyone votes at the same time and the facilitator reveals. There is no asynchronous mode. The app also has no chat or call of its own — use your usual meeting tool alongside it.
Jira refused the write because the estimation field is not available on that work item type’s edit screen. This is a Jira configuration matter, not an app fault. Follow Jira configuration; in team-managed projects the setting lives under Project settings → Features → Estimation.
Into the field selected in step 1 of the wizard: the Story Points field, or the original estimate of the work item’s time tracking. Nothing else in Jira is modified.
Only until the first estimate is saved. After that both are locked, because changing them would give the values already written to Jira a different meaning. Everything else — name, privacy, facilitator, estimators, spectators, backlog — stays editable.
Story Points is a numeric Jira field, so the app offers only numeric decks for it. With Original estimate the sizes are converted before the write — XXS 0.5, XS 1, S 2, M 3, L 5, XL 8, XXL 13 — and saved in hours. The room reports what was actually written.
No. Deleting a game removes the game, its backlog and its votes. Estimates already written to work items stay in Jira.
A public game — anyone who can open the app. A Private game — only its facilitator, estimators and spectators; for anyone else it does not appear in the list and a direct link returns Game not found or deleted.
No. Every read goes through Jira with that user’s own permissions.
No. It is a Forge app running on Atlassian infrastructure with no servers of its own, and it declares no external permissions, so the platform blocks outbound calls entirely. See the Privacy Policy.
No. It runs a JQL search over your own Jira for similar, already estimated work items, takes the median and snaps it to the nearest card in the deck. No model and no external service are involved.
Reload the page with Ctrl+Shift+R (Cmd+Shift+R on macOS) to clear the cached app frame.
The room refreshes every few seconds, and polling pauses while the browser tab is in the background. Switching back to the tab refreshes it immediately.
A finished game is read-only by design — voting, revealing, the timer and editing are all rejected. Its report and CSV export remain available. To estimate the same work items again, clone the configuration into a new game from the ⋯ menu.
Still stuck? See Support.
← Jira configuration · Documentation home · Privacy Policy →