Planning Poker import guide
Export Azure DevOps tickets to CSV for Planning Poker
Bring Azure Boards work items into Planning Poker with a CSV export. Work item IDs stay in the card text so your team can match each saved estimate to its original ticket.
1. Export from Azure DevOps
- In your Azure DevOps project, open Boards → Queries. Open or create a query for the work items you want to estimate; a flat list is easiest to review.
- Include ID and Title in the query columns. Other columns such as Work Item Type, Assigned To, State and Tags can stay in the export.
- Run the query, open its actions menu and choose Export to CSV. Save the downloaded data.csv file with its header row intact.
2. Import into Planning Poker
- Create or join a Planning Poker room, then open Cards.
- Expand Add Cards, select Upload CSV, then choose your export.
- 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
Title becomes the card title, with ID added in front: ADO #272 · Add saved payment methods. Extra columns, including HTML Description text, are ignored. Hierarchical files using Title 1, Title 2 and other numbered title columns are also supported: each row becomes a card using its first nonblank title. Parent-child relationships are not imported.
ID,Work Item Type,Title,Assigned To,State,Tags
272,User Story,Add saved payment methods,,New,paymentsFAQ
Are Azure DevOps descriptions and existing estimates imported?
Only the title and work item ID are used. Description, Story Points, Effort and other fields are ignored. A blank ID is allowed; that card uses its title alone.
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.