Planning Poker Is Now Inside Jira — No Tab Switching Required
If your team runs Jira, sprint planning has always had an invisible tax. You open pointpoker.co in one tab. You open Jira in another. You copy a story title across. You switch back. You vote. You switch again to record the result. You do this 15 times in a row, every sprint, every week. It's not a big thing. But small friction compounds. And it's completely unnecessary. PointPoker is now available on the Atlassian Marketplace — free, with no per-seat pricing — as a native Forge app embedded directly inside Jira.
How it works
Open any Jira issue. The PointPoker panel is right there in the issue sidebar. No new tab, no link to share, no tool to switch to. Your team is looking at the story and the poker session at the same time, in the same place.
Start a session from any issue.
The story context is already there. You open the issue and start the session. Team members who are in Jira will see the session start directly from the same issue panel and can join right there without leaving Jira. If anyone prefers the richer web experience, they can join the same room through pointpoker.co instead — same session, same real-time votes, their choice. No one gets left out either way.
Real-time voting with live progress tracking.
A live progress bar shows who has voted and who hasn't. No more "has everyone voted?" before the reveal. You can see it.
Everyone reveals at the same time.
Same simultaneous reveal that makes PointPoker work — no anchoring, no one pulling estimates toward theirs before the cards flip.
Role-based vote analysis.
PointPoker's role-based grouping — votes split by Dev and QE — comes fully into the Jira integration. You can see immediately whether your developers and testers are aligned, or whether there's a gap worth discussing. A role gap warning surfaces automatically when the difference is significant. A vote distribution histogram gives you the full picture at a glance.
One-click write-back to Jira.
When your team reaches consensus, one click saves the agreed story point value directly to the Jira Story Points field. No switching tabs, no manual update, no forgetting to record the result after the meeting.
Automatic session summary with @mentions.
After each session, a summary comment is added to the issue automatically — including who participated, what they voted, and what was agreed. The whole estimation record lives on the issue where it belongs.
Why we built it this way
The philosophy behind PointPoker has always been the same: meet teams where they are. Don't ask them to change how they work to fit a tool. Don't add steps to a process that already has enough of them. Jira is where most teams live. Their stories are there, their backlog is there, their sprints are there. Building a PointPoker experience that lives outside of Jira and asks teams to context-switch was always a compromise. This removes that compromise entirely. The Forge app is a thin shell over the same PointPoker backend that teams are already using. Same real-time sync. Same zero-friction voting. Same ad-free experience. Just delivered where your team already is.
It's free on the Atlassian Marketplace
No cost. No per-seat pricing. No trial that expires. The PointPoker Jira app is free on the Atlassian Marketplace, consistent with how every core PointPoker feature has always been priced.
Already using PointPoker without Jira?
The standalone tool at pointpoker.co isn't going anywhere. No signup, works in any browser, still the fastest way to get a remote team estimating in under 30 seconds. The Jira app is an addition, not a replacement — for teams that want the tighter integration, it's there. For teams that don't use Jira, nothing changes.
Install PointPoker on the Atlassian Marketplace
Free, no per-seat pricing. Works with Jira Cloud.
Install Free on Marketplace