Planning Poker import guide

Export Jira tickets to CSV for Planning Poker

Bring Jira stories into a Planning Poker session without retyping them. Export your search results as CSV, preview the cards, and keep issue keys alongside each estimate.

Start Planning PokerImport from Azure DevOps

1. Export from Jira

  1. In Jira Cloud, open Filters → Search work items and filter the stories you want to estimate. You can also open your project's List view.
  2. Open the More actions menu (three dots), choose Export, then Export CSV — all fields. Menu names can vary between Jira versions. If you use a current-fields export, include Summary and Issue key (or Work item key).
  3. Save the CSV file. Keep its header row and UTF-8 encoding; there is no need to remove extra columns.

Atlassian’s Jira Cloud CSV export instructions

2. Import into Planning Poker

  1. Create or join a Planning Poker room, then open Cards.
  2. Expand Add Cards, select Upload CSV, then choose your export.
  3. Review the preview, including ticket IDs. Select Import to add the cards, or Cancel to leave the room unchanged.

How ticket IDs and titles appear

Summary becomes the card title. Issue key, Work item key or Key is prefixed to it, for example PAY-123 · Add saved payment methods. The readable key takes priority over Jira's numeric Issue id; if only the numeric ID is available, we use Jira #12345. Long Description fields and repeated Comment columns are ignored.

Summary,Issue key,Issue id,Issue Type,Status,Description
Add saved payment methods,PAY-123,10001,Story,To Do,Full acceptance criteria
Download a sample Jira CSV

FAQ

Will Jira descriptions or existing story points be imported?

We use Summary, even when Description is present. Existing estimates, attachments, comments and other fields are not imported. The cards start unestimated so your team can vote together.

What are the import limits?

Choose a comma-separated UTF-8 CSV up to 1 MB, with at most 100 nonblank cards. Each card can contain up to 500 characters, including its ticket ID prefix. Split larger exports into smaller files. Oversized cards are rejected rather than truncated.

What happens when I confirm the import?

Preview the cards before confirming. Import appends them in file order and clears current votes. Existing cards remain. Reimporting the same file adds another copy; ticket IDs are references in editable card text, not a synchronization or deduplication key.

Can I export the estimates back to my tracker?

Export CSV in Results or beside Leave Session on the Board downloads all cards with Description, Result and Status. Ticket IDs remain in Description alongside saved results. This is a recap file, not a tracker-ready update file: it does not automatically update Jira or Azure DevOps. Reimporting it here creates new unestimated cards.

Why is my CSV rejected?

Keep the original header row and comma delimiter. Supported headers are English and case-insensitive. Check the file and card limits shown above. Fields containing commas, quotes or newlines must be quoted correctly; native CSV exports handle this for you. Generic files can use Description, Title or Summary.