Ridgeline Apps

Planning Poker for Jira

Your team estimates together, live or on their own time, and each final estimate saves straight to the issue's story points. This page covers how to get help, how the app works, and what it does with your data.

Get support

Email us with your Jira site address (for example yourteam.atlassian.net), what you were doing, and any message the app showed. A screenshot helps.

Email[email protected]

Support hoursMonday to Friday, 9 am to 5 pm US CentralWe reply within one business day.

Bugs and ideasSame addressFeature requests are read and answered.

Getting started

Open a project. After install, every Jira project gets a Planning Poker item in its sidebar (on some sites it sits under Apps).
Start a session. Click New session, name it, and pick the issues: the backlog, a sprint, a saved filter, or pasted issue keys and links.
Choose live or async. Live walks the team through one item at a time. Async lets everyone vote by a deadline; an item reveals once everyone you invited has voted.
Pick a deck. Fibonacci, modified Fibonacci, T-shirt sizes (saved as 1, 2, 3, 5, 8, 13 points) or your own cards.
Vote, reveal, decide. The facilitator reveals the cards, sees the spread and a suggested estimate, then picks the final value or asks for a re-vote.
It saves itself. The final estimate goes into the issue's story points field and a comment records everyone's votes. Each issue's Planning Poker estimates panel shows its history.

Common questions

An item says it can't take story points. What do I do?

Before a session starts, the app checks every issue for a story points field it can write to. If an issue type has no story points field on its edit screen, the warning names the issue and the fix: a Jira admin adds the field to that issue type. Click Check again afterwards. Nothing is lost while you fix it.

Who can vote, and who controls the session?

Anyone who can view the project can join and vote. The person who starts a session is its facilitator: only they can reveal, set final estimates, add issues, close or delete it. Estimates are saved as the facilitator, so they need permission to edit the issues.

Does it work with team-managed and company-managed projects?

Yes, both. The app finds the Story Points or Story point estimate field your project uses.

Can I use it on my phone?

Use Jira in your phone's web browser. Jira's mobile app does not show Forge apps yet, which is an Atlassian limitation.

Can I export results?

Yes. Each session has an Export CSV button with every issue, the final estimate and each voter's card.

How much does it cost?

Pricing is shown on the Atlassian Marketplace listing and billed by Atlassian with your Jira subscription. Every plan starts with a free trial.

Privacy policy

Effective 10 November 2026

Planning Poker for Jira is made by Ridgeline Apps, a trading name of Promise Land Provision LLC, Missouri, USA ("we"). It is built on Atlassian Forge and runs entirely on Atlassian's cloud. We do not run servers of our own, and the app sends no data outside Atlassian.

What the app stores

Data	Why	Where
Session details: name, project, issue keys, issue summaries and types, deck, deadline	To run the session	Forge storage on Atlassian's cloud, inside your Jira site's app data
Atlassian account IDs of the facilitator, invited people and voters	To know who voted and who controls the session	Same
Each vote (card and time) and the final estimate	To reveal results and keep estimate history	Same

Names and avatars are looked up from Jira when shown and are not stored. The app does not collect email addresses, passwords, payment details, IP addresses or analytics, and uses no cookies or tracking.

What the app writes to Jira

When a facilitator confirms a final estimate, the app writes it to the issue's story points field and adds a comment with the votes. These become part of your Jira data and follow your site's own retention.

Who can see it

People with access to the project in your Jira site.
We cannot see your sessions, votes or issues. Forge storage is not readable by app developers.
Atlassian hosts the data as described in its own privacy policy and Forge terms.

Retention and deletion

Deleting a session removes its stored details and votes. Estimate history shown on issues stays until the issue is deleted.
Uninstalling the app makes its stored data inaccessible, and Atlassian deletes it under its standard Forge data retention process.
To ask about or remove data, email the support address above.

Data residency

The app stores data with Atlassian, which places Forge app data according to your site's data residency settings where Atlassian supports it.

Changes

If this policy changes, we will update this page and its effective date.

Security

Runs on Atlassian Forge with no outside servers or network calls.
Asks only for the Jira permissions it needs: read and edit issues, read users, read boards and sprints, and its own storage.
Jira requests run as the signed-in person, so Jira's own permissions apply.
Report a security concern to [email protected] with "Security" in the subject. We reply within one business day.