Home / Guides / Planning poker for Jira

Planning poker for Jira

You don’t need a Jira plugin to estimate a Jira backlog together. Export the issues, import them into a PointHuddle room, vote, and take the estimates back. Nobody needs a Jira license or an account to join.

1. Export the issues from Jira

1. Open the issues you want to estimate: a filter, a board backlog query or a JQL search such as project = PP AND sprint in futureSprints().
2. Choose Export and pick a CSV or XML export.

Any CSV works, so the same steps fit Linear, GitHub, Azure DevOps or a spreadsheet.

2. Import them into a room

1. Create a room and open the story panel.
2. Click Import from CSV or Jira and choose the file, or drop it on the dialog. CSV, TSV and Jira XML are accepted, up to 100 stories at a time.
3. A Jira export is recognised: the summary becomes the title, the issue key is shown before it and the description comes along. For other files, pick the title, key and description columns yourself.
4. Check the preview and import.

3. Link stories back to Jira

In Room settings → Issue links, set the issue URL template, for example https://acme.atlassian.net/browse/{key}. Every key like PP-118 in the queue, the history and the export then links to the issue.

4. Estimate

Run the session as usual: everyone votes in private, the cards are revealed together and the table shows how far apart the votes are. Turn on Auto-start next story to move through the queue after each accepted estimate.

5. Take the estimates back

Open the Summary tab and use Copy table or Download CSV. Each row has the story with its issue key, the final estimate and a link to the issue. Paste the values into Jira’s story point field, or use a bulk update. If your team posts to Slack or Microsoft Teams, each estimate can also go to a channel as it is accepted.