Your Jira backlog is already open. Stop typing it out by hand.
Quick answer
The PointPoker Chrome extension scans your open Jira tabs, pulls every story title into a planning poker session as a queue, and lets your team vote through them in order — no copy-pasting, no tab-switching, no manual entry.
Every sprint planning meeting follows the same ritual: someone opens Jira, reads out a story title, then switches to the poker tool, types it in, and repeats fifteen times. The PointPoker Chrome extension eliminates that ritual entirely. It reads your open Jira tabs and sends every story title straight into your session — so you start estimating in seconds, not minutes.
The Problem: Manual Copying Kills Momentum
Planning poker should be about focused discussion and fast consensus, not administrative overhead. Yet for most teams, the first ten minutes of every session are spent building the queue. For a ten-person team running two-week sprints, that setup overhead can consume fifteen to twenty minutes per planning cycle.
How the PointPoker Chrome Extension Works
The extension integrates directly with the PointPoker web app. Once installed, it adds a small button to your browser toolbar. When you are on a Jira board or have multiple Jira issue tabs open, clicking the button detects every story or issue visible. It extracts the story keys and titles, then imports them as a queue into your active PointPoker session. No API credentials required, no OAuth setup, no Jira admin permissions needed. It works with any Jira instance: Jira Cloud, Jira Data Center, or any company-hosted deployment.
Step-by-Step Setup
Install the extension from the Chrome Web Store — search for PointPoker Jira Queue. Open your Jira sprint backlog or individual issue tabs. Go to pointpoker.co, create a session, and open the extension popup. Select the stories you want, or select all, and click Import. The stories are added to your session queue immediately.
Working With the PointPoker Web App
The Chrome extension works exclusively with the PointPoker web app — not with a Jira Forge embedded panel. This is intentional. Your session lives at pointpoker.co, where your full team joins by link, regardless of whether they have Jira access. Observers, stakeholders, and team members who only need to vote do not need Jira accounts at all.
Tips for Managing Large Backlogs
If your sprint backlog contains thirty or forty stories but you only plan to estimate a subset, open only the Jira tabs for the stories you actually want to vote on. For teams that run recurring sessions, create a saved Jira filter for unestimated stories. The extension aggregates across all open Jira tabs regardless of project key.
Install the Chrome Extension
Works with any Jira instance. No API keys or admin access required.
Add to Chrome — Free