Documentation

Overview

Planning Poker for Jira is a Forge app that runs a Fibonacci-card estimation round directly on a Jira issue. A host opens a session from the issue's Planning Poker panel, teammates vote privately, the host reveals all votes, and the agreed Story-Point value is pushed back to the issue's configured custom field. The previous Story-Point value (if any) is preserved into the Original Story Points field so historical estimates are never lost.

Install

1. From your Jira site, open Apps → Explore more apps.
2. Search for Planning Poker for Jira and click Get it now.
3. Approve the requested scopes: read:jira-user, read:jira-work, write:jira-work, storage:app. These let the app read issue and field metadata, write the agreed Story-Point value back to the issue, and persist per-project settings in Atlassian-managed storage.

No external accounts, API tokens, or shared secrets are required. The app runs entirely inside Atlassian's Forge runtime.

Configure (per project)

Each Jira project picks its own Story-Point field and which issue types are allowed to host a session.

1. Open Project settings → Apps → Planning Poker.
2. Story-Point field: select the custom field where the agreed value should be written. If your project uses Jira's standard field, it appears as Story point estimate (typically customfield_10016).
3. Allowed issue types: tick the issue types that can host a session (commonly Story, Task, Bug). The panel will be hidden on other types in this project.
4. Click Save. Settings are stored in Forge KVS, scoped to the project.

Run a session

1. Open any allowed issue. The Planning Poker panel appears in the right-hand column.
2. The first participant clicks Start session — this person becomes the host.
3. Other teammates open the same issue and join automatically when the panel loads.
4. Each participant picks a Fibonacci card (0, 1, 2, 3, 5, 8, 13, 20, 40, 100, ?). Votes stay hidden until reveal.
5. The host clicks Reveal to show all votes side-by-side.
6. When the team agrees on a value, the host clicks Push SP. The agreed number is written to the configured Story-Point field on the issue. Any existing Story-Point value is moved into Original Story Points first.
7. The host clicks End session to close the round.

Permissions & data

All Jira reads and writes are made on behalf of the signed-in user (api.asUser()) — the app never elevates above your own permissions. No data leaves Atlassian's Forge runtime: session state, votes, and per-project settings live in Forge KVS, which is managed by Atlassian inside your Jira instance's region.

For the full data inventory and retention policy, see the Privacy Policy. To report a vulnerability, see the Security page.

Support

For questions, bug reports, or feature requests, email lingxuan.kee@yycadvisors.com with the subject prefix [Planning Poker]. Once the Marketplace listing is live, the Get support form on the listing page is also a valid channel and will route to the same address.