Free Excel to Jira sample workbook and import template
Use these samples as starting points for Jira import planning. The XLSX workbook shows a realistic multi-sheet backlog handover with mapping notes, while the CSV template is useful when you need a simple flat file.
Download the samples
The XLSX sample includes synthetic backlog rows, parent references, update examples and mapping notes. The CSV template keeps the same planning idea in a lightweight flat format for native Jira CSV import preparation.
What is in the XLSX sample workbook
The workbook contains three sheets: Backlog import for synthetic Jira-ready rows, Mapping notes for suggested field mapping, and How to use for safe import/update guidance. It is designed for evaluation and adaptation, not for uploading unchanged into a production Jira site.
What each column is for
| Column | Purpose | Adaptation note |
|---|---|---|
| Summary | Main Jira issue title | Usually required. |
| Description | Main issue body | Can be combined with other columns in Description Builder. |
| Issue Type | Story, Task, Bug, Epic or Sub-task | Use issue types available in the target project. |
| Priority | Initial priority | Match Jira priority names or clean values before import. |
| Assignee and Reporter | User fields | Use values Jira can resolve. |
| Due Date | Deadline or planned date | Use an unambiguous date format. |
| Labels and Component | Classification | Keep values consistent. |
| Epic Name, Parent Key | Hierarchy hints | Validate against Jira project configuration. |
| Linked Issue Key | Relationship planning | Use only when links are intended and supported. |
| Story Points | Estimate | Map only if the field exists for the issue type. |
How to adapt it to your Jira project
Start with required Jira fields, then add only the columns your team actually needs. Remove columns that are not used by your project. If a workbook already has useful business columns, keep them and decide during mapping whether they belong in Jira fields or in Description Builder.
Why the app does not require a perfect template
The app is designed for real workbooks. You can choose worksheet and header row, map columns manually, clean values and review rows before import. A template helps teams align, but the workflow should still handle revised files and workbook structures that are not identical.
Related guides
Use the sample as a starting point
Adapt the workbook to your Jira project, then use the product workflow to map, validate and review the file against your Jira configuration.