Planning TablePlanning poker your whole team shows up for
Planning Table runs estimation sessions inside Jira: live, async or bucket-sized. Pull in work items by sprint or JQL, vote with every card hidden until the reveal, talk through the outliers, and save the agreed estimate to Story Points.
Read the setup guideSee the three modes
Three ways to run a session
Same scales, same stats, same save-to-Jira finish. Pick the mode that fits how your team meets.
Interactive
A live room. Everyone votes on the same work item with cards hidden until the facilitator reveals, or auto-reveal flips them the moment everyone estimating has voted. Discussion timer, re-vote rounds and spectator mode included.
Async
No meeting needed. Everyone votes the whole list at their own pace, across time zones. You can see who is done, but values stay hidden from everyone, including the facilitator, until voting is closed.
Bucket sizing
The fastest way through a big backlog. The team drags work items into buckets on a shared board, with moves showing for everyone within seconds, then turns the buckets into finals and saves them all at once.
Built for how teams actually estimate
Everything around the vote is there to shorten the argument, not the thinking.
Timer and auto-reveal
A 1:00, 2:00 or 5:00 discussion timer keeps debates boxed, and optional auto-reveal ends the "are we all in?" wait.
Stats that settle debates
On reveal: distribution, average, median, agreement, consensus and a suggested final, the scale value nearest the median. The ? and coffee cards never skew the numbers.
Any scale you like
Fibonacci (0-100), T-shirt sizes, powers of two, 1-10, or your own custom scale of 2 to 20 values. Chosen per session.
Reference work items
Not sure what a 5 feels like? See your team's existing work items at each scale value while you vote, so estimates stay consistent sprint to sprint.
Context in the room
Each work item shows its description, status, priority, labels and current estimate, so nobody has to click out to Jira mid-vote.
Finals saved to Jira
Save to Story Points or any number field, as the facilitator, so Jira permissions and history apply exactly as if you edited the work item yourself.
Pick work items fast
Use the current sprint or open work items in one click, or write JQL with autocomplete, validation and a preview. Up to 50 work items per session.
Your data stays put
Runs on Atlassian. Sessions and votes stay on your own Atlassian site, with no outside servers, no analytics and no AI.
How it works
From install to saved estimates in one planning slot. Full step-by-step instructions are in the documentation.
- Install Planning Table from the Atlassian Marketplace on your Jira Cloud site.
- Open the app from Jira's Apps menu: Planning Table - Planning Poker.
- Create a session: pick a mode, a scale, the field to save to and up to 50 work items.
- Vote: teammates join from the same Apps menu and pick their cards, hidden until the reveal.
- Reveal and review the distribution, agreement and suggested final.
- Save finals to Story Points or any number field, then move to the next work item.
Frequently asked questions
How much does Planning Table cost?
Planning Table is free for up to 10 users. Above that it is priced per user per month on the Atlassian Marketplace, billed by Atlassian, with a 30-day free trial on paid tiers. The app never collects payment details.
Does my estimation data leave my Atlassian site?
No. Planning Table runs entirely on Atlassian's platform and is eligible for Runs on Atlassian. Sessions, votes and results stay in app storage on your own Atlassian site. Nothing is sent to outside servers, and there are no analytics, no AI and no third-party services. Wattlebrooks Apps cannot see your data.
Who can facilitate a session?
Anyone who can open the app can create a session, and the person who creates it facilitates. Only the facilitator can reveal votes, start a re-vote, run the timer, set finals, save to Jira, close voting and delete the session. Everyone else votes, or watches as a spectator.
Can anyone see a vote before the reveal?
No. Until the reveal, the room only shows who has voted, never what they voted. In Async mode vote counts are visible so you can track progress, but the values stay hidden from everyone, including the facilitator, until voting is closed.
Why does my JQL show an "add a search restriction" error?
Jira Cloud rejects unbounded JQL queries. Add a restriction such as a project, sprint or assignee, for example: project = ABC AND sprint IN openSprints(). The JQL box has autocomplete, validation and a preview, so you see exactly which work items a query selects before you create the session.
Can I use T-shirt sizes if my estimate field is a number field?
Yes. You can run a session on any scale, and the agreed final is recorded in the session either way. Jira estimate fields hold numbers, so only numeric finals (Fibonacci, powers of two, 1-10 or a numeric custom scale) are written to the field. T-shirt and other text finals stay in the session as your team's record.
Can people watch a session without voting?
Yes. Turn on Spectate to watch without estimating. Spectators see everything the room sees, are not counted in the voted total and never hold up auto-reveal.
Does Planning Table work with team-managed projects?
Yes. Team-managed and company-managed projects both work. You can estimate work items from any project you can browse, and finals are saved as the facilitator, so your normal Jira permissions always apply.