Team backlog estimation inside Jira Cloud — user guide, privacy policy and support.
Planning Poker needs no settings of its own — there is no admin screen to fill in. What it does need is a Jira field it is allowed to write to. This page covers that, and the Jira permissions the participants need.
← Documentation home · Manage games
When the facilitator saves a final estimate, the app writes it to Jira as the facilitator, using their own Jira permissions, into the field chosen for the game:
| Estimation field of the game | Jira target |
|---|---|
| Story point estimate | The Story Points field of the work item — the app looks for a field named Story Points or Story point estimate on your site |
| Original estimate | The original estimate of the work item’s time tracking, in hours |
If the direct write fails because the field is not on the work item’s edit screen, the app makes one more attempt for Story Points: it writes through the board the work item belongs to, into the estimation field configured on that board. Only if both attempts fail does it report an error — and the message names the cause.
The Story Points field exists on the site, but it has to be on the screen used by the work item type you estimate.
Team-managed projects use the Story point estimate field, and it appears only when estimation is switched on.
The board fallback works when the board of the project has an estimation field set:
This is what lets the app save an estimate even when the field is missing from the edit screen.
Original estimate is part of Jira’s time tracking.
Values are written in hours, for example 5h. Cards from the Time
estimates deck are written as they are (2d, 1w).
The app never grants access to anything a user could not already open in Jira. So participants need, in the projects being estimated:
| Permission | Why |
|---|---|
| Browse projects | To see the work items in the backlog and in the game room |
| Edit issues | For the facilitator only — to write the final estimate |
If a participant is missing Browse projects, they will join the game but see nothing to estimate. If the facilitator is missing Edit issues, Jira rejects the write and the app shows the error.
The app requests the Jira scopes it needs to read the backlog and write a single field: read access to projects, work items, JQL and users, write access to work items, board read access for the estimate fallback and the Go to Board link, and Forge storage for the games themselves.
It declares no external permissions. That means the platform itself prevents it from making any outbound network call — see the Privacy Policy.