Scrum Poker for Jira

Storyvote is free scrum poker (planning poker) that works with Jira Cloud. Import a sprint's or the backlog's issues as stories, estimate them together with hidden votes, and each final estimate lands back on its issue: in its story points field and as a comment. No Storyvote account, no Marketplace app to install, and no paid plan.

How it works

1. Create a room.Start one in your browser and share the link. Teammates join with their name, no sign-up and no Jira seat needed.
2. Connect Jira. As the host or a facilitator, open the Stories panel's "⋯", choose Import from a tracker, then Jira and Connect Jira. You sign in on Atlassian's own page, in a small window, pick your Jira site and allow the room to read your projects and comment on their issues.
3. Pick a project and its issues. Choose the backlog, the active sprint, the future sprints or every open issue, in your board's order. Search and tick the ones to estimate (a sprint comes in whole at first); issues already in the room are left out, so importing again only adds what's new. Pick disciplines (frontend, backend, QA…) to split every story, or none, and press Import.
4. Estimate. Each issue becomes a story with its key (SCRUM-42) as the ticket and a link back to the issue. Vote, reveal and agree on the estimate as in any room, live on a call or async across time zones.
5. See it on the issue. Pick "Write estimate to Jira" in a story's "⋯" menu, or turn on automatic write-back when you connect, so each final estimate goes a few seconds after it is set. It fills in the issue's story points field (Story point estimate, or Story Points), and appears as a comment: "Estimation: 5", or for a split story "Estimation:" with a line per discipline (Frontend: 3, Backend: 5), then the answers to any extra questions (AI tokens: 250k), ending with a small "Estimated with storyvote.app" link. A split story's points are the total. Write it again after a change (or let write-back do it) and both follow: the field is updated and the same comment edited, so an issue never collects a pile of them. An estimate that isn't a number (a T-shirt size, "?") goes in the comment only, as does one on an issue whose points you can't edit.

New to running the meeting itself? Our sprint planning guide has an agenda to start from.

What you get

• No copying keys and titles across. A sprint or a slice of the backlog comes in at once, up to 200 issues at a time, and the estimates go back without anyone pasting them into Jira.
• The whole room. Hidden votes until the reveal, a discussion timer, custom decks, extra questions (risk, clarity, Agent-ready, AI tokens) and stories split by discipline: everything a room offers works on imported issues too.
• The connection belongs to the room. One person connects, and the whole room benefits: nobody else needs a Jira account to vote. Whoever connected stays the author of the comments.
• Nothing to install on your site. Storyvote isn't a Jira plugin: it asks for access when you connect, like any app that signs in with Atlassian, and it shows among the apps connected to your Atlassian account, where you can revoke it at any time.
• Free, with no limits. Unlimited players, rooms and stories. There is no paid plan and you are never asked for a credit card.

The connection is for Jira Cloud (your-team.atlassian.net). On Jira Data Center or Server, export the issues as CSV and import the file instead: Storyvote reads the Summary and Issue key columns.

Privacy

When you connect, Atlassian asks you to let Storyvote read your projects and issues, comment on issues and read your name. Atlassian then gives the room access tokens, which Storyvote keeps encrypted on its server: they never reach anyone's browser. Storyvote reads only the projects and issues you pick, writes only their story points and its estimate comments, which stay in Jira, and doesn't store your Atlassian account's ID or name. Press Disconnect in the import window, or end the room, and Storyvote deletes the tokens; a connection left unused is deleted after 30 days. Read more in our privacy policy.

The Jira connection is new. It runs in the browser, not inside Slack, Discord or Telegram, since signing in opens a window of its own. If something looks off, we'd like to hear about it.