🚀 Overview
Planning Poker for Jira is a free Atlassian Forge app that brings story point estimation directly into your Jira issues. Your team votes on effort using playing cards, the moderator reveals votes, and the agreed story points are saved to the ticket — all without leaving Jira.
Built entirely on the Atlassian Forge platform. No external servers, no data leaves Atlassian's infrastructure, and no additional accounts are required.
Free for teams up to 15 participants per session. Upgrade to Pro for unlimited participants.
DEV-42
🔢 Fibonacci
Team
Your Vote
✨ Features
4 Voting Decks
Fibonacci, T-shirt sizes, Powers of 2, and Sequential — switch any time.
Hidden Votes
Votes stay hidden until the moderator reveals them, preventing anchoring bias.
Participant Tracking
Real-time view of who has voted and who hasn't, with a live progress bar.
Nudge Non-voters
Post a Jira @mention comment to remind teammates who haven't voted yet.
Auto-Reveal
Automatically reveal votes the moment everyone has cast their card.
One-click Story Points
Save the consensus estimate directly to the Jira Story Points field.
Results Summary
Average, median, consensus, and a vote distribution bar chart.
Custom T-shirt Mapping
Map XS–XXL to your own story-point values. Saved per user to your account.
Moderator Controls
Reveal, reset rounds, change decks, and end sessions — moderator only.
💰 Plans & Pricing
Planning Poker for Jira uses a simple freemium model managed through the Atlassian Marketplace.
Licensing is handled automatically by Atlassian. Once you have an active Marketplace license, the 15-participant cap is removed. No configuration required — the app detects your license status on each request.
How Licensing Works
| Install Type | Participant Limit | License Check |
|---|---|---|
| Free (no license) | Up to 15 per session | The 16th joiner sees an upgrade prompt and cannot vote |
| Pro (active Marketplace license) | Unlimited | Atlassian passes license.isActive = true to the app on every request |
| Evaluation / trial | Unlimited during trial | Same as Pro — trial license is treated as active |
🔧 Setup Guide
Follow these steps to install Planning Poker for Jira on your Jira Cloud site.
Install from the Atlassian Marketplace
Go to Jira → Apps → Explore more apps and search for "Planning Poker for Jira". Click Get app. You must be a Jira site administrator to install apps.
The app requests read:jira-work, write:jira-work, and read:jira-user scopes. These are shown during installation and allow the app to read issue data, update story points, and show participant names.
Enable the Story Points field (if not already active)
The app writes directly to the Jira Story Points field. If your project doesn't show story points, you need to add it to the issue screen.
Company-managed (classic) projects: Go to Jira Settings → Issues → Screens, find your project's screen, and add the Story Points field.
Team-managed (next-gen) projects: Open any issue → click + in the right panel → add Story points.
If you try to set story points on a project where the field hasn't been added, you'll see: "This issue type does not support story points."
Open a Jira issue to start using the app
Once installed, open any Jira issue. You'll see two entry points:
| Entry Point | Location | Best For |
|---|---|---|
| 🃏 Estimate Story Points | Right-hand sidebar | Quick access while browsing issues |
| Agile Effort Estimation (panel) | Bottom panel (above Activity) | Full-width session view for the whole team |
Both entry points share the same session data — you can use either one interchangeably.
🎮 How to Run a Planning Poker Session
Start a session (Moderator)
Open a Jira issue and click ▶ Start Estimation Session. Select a voting deck and optionally enable Auto-reveal. You become the moderator — only you can reveal, reset, change the deck, and end the session.
Planning Poker
Team members join and vote
Team members open the same Jira issue and are automatically added to the session. Each person selects a card. Votes are hidden until the moderator reveals them.
Your Vote
Card 5 selected (tap another card to change your vote before reveal)
Track who has voted
The Team section shows every participant with a green ✓ (voted) or grey … (not yet voted). The progress bar updates in real time. As moderator, click 👋 Nudge next to any non-voter to post a Jira @mention comment.
Team
Reveal votes and review results
Click 👁 Reveal Votes. All votes appear simultaneously with a distribution bar chart, plus Average, Median, and Consensus statistics.
Results
Set Story Points or start a new round
Click 📌 Set Story Points → X SP to write the consensus value to the Jira ticket's Story Points field. If the team disagrees, click 🔄 New Round to reset and vote again.
Once story points are saved, a green ✓ confirmation appears and the button is disabled to prevent accidental double-saves.
🃏 Voting Decks
The moderator can switch decks at any time by clicking the deck badge in the session header. Switching resets all current votes.
| Deck | Values | Best For |
|---|---|---|
| 🔢 Fibonacci (default) | 0 1 2 3 5 8 13 21 ? ☕ |
Most teams — reflects natural uncertainty at larger sizes |
| 👕 T-shirt Sizes | XS S M L XL XXL ? |
Teams new to estimation; maps to numeric story points automatically |
| 2ⁿ Powers of 2 | 1 2 4 8 16 32 ? |
Technical teams who think in doubling increments |
| 🔟 Sequential | 1 2 3 4 5 6 7 8 9 10 ? |
Simple linear scale for straightforward tasks |
🖋 Customizing T-shirt Point Values
When using the T-shirt deck, each size (XS, S, M, L, XL, XXL) is automatically converted to a numeric story-point value when you click Set Story Points. The default mapping is a Fibonacci-inspired scale, but you can customize it to match your team's convention.
Default mapping
| T-shirt Size | Default Story Points |
|---|---|
| XS — Extra Small | 1 |
| S — Small | 2 |
| M — Medium | 3 |
| L — Large | 5 |
| XL — Extra Large | 8 |
| XXL — Double Extra Large | 13 |
How to customize
Before a session (Setup view)
Select the T-Shirt deck on the setup screen. A ⚙ Customize point values panel appears below the options. Expand it, edit the values, and click 💾 Save Mapping before you start the session.
After reveal (Results view)
Once votes are revealed, a ⚙ Customize point values collapsible panel appears below the Set Story Points button. You can adjust the mapping and save it before clicking Set Story Points.
Mappings are saved per user to your Atlassian account via Forge Storage. Your custom values persist across sessions and Jira sites. Other team members keep their own settings independently.
📌 Story Points Configuration
The app tries two common Jira field IDs automatically — no configuration needed for most projects:
| Project Type | Field ID Used |
|---|---|
| Team-managed (next-gen) | story_points |
| Company-managed (classic) | customfield_10016 |
The app tries story_points first, then falls back to customfield_10016. If both fail, the Story Points field hasn't been added to your project's screen — see Setup Step 2.
🔒 Permissions & Data
| Permission | Why it's needed |
|---|---|
read:jira-work |
Read issue ID and key to display in the session header |
write:jira-work |
Update the Story Points field and post @mention comments when nudging |
read:jira-user |
Fetch participant display names for the Team section |
storage:app |
Store session data (votes, participants, T-shirt mappings) in Forge's encrypted key-value store |
Privacy: No data is sent to external servers. All session data lives in Atlassian's Forge Storage and is automatically deleted when the moderator ends the session.
❓ Frequently Asked Questions
Who becomes the moderator?
The first person to click Start Session on a Jira issue becomes the moderator. Only the moderator can reveal votes, reset rounds, change the deck, and end the session.
How many people can join a session?
The Free plan supports up to 15 participants per session. The 16th participant will see an upgrade prompt. With a Pro license (purchased via Atlassian Marketplace), there is no participant limit.
What's included in the Pro plan?
Pro removes the 15-participant cap and unlocks unlimited participants per session. All other features (all decks, auto-reveal, nudge, T-shirt mapping, story point save) are available on the Free plan. Licensing is managed entirely through the Atlassian Marketplace — no additional accounts needed.
Can multiple issues have active sessions simultaneously?
Yes — sessions are independent per Jira issue. Each issue has its own separate session state and participant list.
What happens if the moderator leaves?
Participants can still vote, but only the moderator can reveal or reset. If the moderator is unavailable, a Jira admin can start a new session on the same issue — the old data is overwritten.
Can I change my vote before reveal?
Yes — tap a different card at any time before the moderator clicks Reveal. Your vote updates immediately.
Why doesn't "Set Story Points" work?
The Story Points field must be added to your project's screen. See Setup Step 2. If the field is present but you get a permission error, ensure the user clicking the button has edit rights on the issue.
The app shows a blank panel — what do I do?
Press Cmd+Shift+R (Mac) or Ctrl+Shift+R (Windows) to hard-refresh the page. If the issue persists, open the issue in an Incognito/Private window.
Does my custom T-shirt mapping apply to everyone on my team?
No — T-shirt mappings are personal. Each user saves their own mapping, and it's applied when they click "Set Story Points". This gives each user flexibility without affecting teammates.
📡 Support
Found a bug or have a feature request? Open an issue on GitHub: