Import and update Jira issues from real Excel workbooks without reshaping everything into a perfect CSV template. Upload the workbook, map columns to Jira fields, build descriptions from multiple columns, preserve hierarchy, validate every row, then create or update selected Jira issues safely.
Free trial and billing are handled by Atlassian Marketplace.
Jira CloudAtlassian ForgeXLSX/XLS/CSVValidate before importReusable mappingsImport report
From real Excel workbook to reviewed Jira issues.
Latest product updates
Actively improved through Marketplace releases
The latest Marketplace release refreshes supporting dependencies with current security fixes while keeping the app's permissions, data handling and import workflow unchanged.
Watch a short walkthrough showing how to import an Excel workbook into Jira Cloud, map spreadsheet columns to Jira fields, review changes, and create or update Jira issues safely.
The video shows selecting an Excel workbook, choosing a worksheet and header row, mapping Excel columns to Jira fields, reviewing planned Jira changes before import, and creating or updating Jira issues only after confirmation.
Import Excel to Jira without rebuilding your workbook as a perfect CSV
Jira's native import flow is CSV-based, and that is useful for clean, admin-led one-time imports. Many teams, however, receive real Excel workbooks with multiple worksheets, non-first header rows, notes, estimates, ownership, acceptance criteria and hierarchy.
Excel to Jira Importer and Updater lets users start from XLSX, XLS or CSV files. Choose the worksheet and header row, map Excel columns to Jira fields, clean values, build structured Jira descriptions, preview planned creates or updates, and import only after review.
The workflow supports creating new Jira issues and updating existing Jira issues from repeated Excel uploads when matching information is available.
Select the worksheet and header row before mapping workbook columns.
Common import problems
Common Excel to Jira import problems
My Excel file has multiple worksheets
Choose the worksheet that contains the Jira import data before mapping columns.
The header row is not the first row
Select the row that contains column names so workbook notes and cover rows do not break the import setup.
I need to import epics, stories and subtasks
Use hierarchy setup when the workbook and Jira project support the planned parent relationships. Read the hierarchy guide.
I need to update existing Jira issues from Excel
Use repeated imports to update matching Jira issues when a stable issue key or supported row identity is available. Read the update guide.
I need to combine several Excel columns into Jira Description
Description Builder can combine context, acceptance criteria, notes and estimates into one structured Jira Description.
I need to clean values before import
Use Value cleanup to normalize spreadsheet values before Jira validation and import.
I need to review changes before Jira is updated
Validate rows and review planned creates, updates, skipped rows and errors before the final import action.
I am not a Jira admin and do not want a complex CSV process
Use the guided workflow and send the Marketplace trial request to the person who approves Jira Cloud apps.
Problem
Your Jira work often starts in Excel. The upload is the painful part.
Client-approved offers, discovery sheets, task lists, estimates and requirement handovers often arrive as real-world Excel workbooks: multiple columns, messy values, notes, acceptance criteria and hierarchy hints. The hard part is moving that workbook into Jira without losing structure, creating duplicates or turning the upload into a manual copy-paste task.
CSV preparation eats time
Jira's native import works best when the data is already clean and CSV-ready. Real handovers rarely are.
Copy-paste creates mistakes
Descriptions, acceptance criteria and estimates get lost or pasted into the wrong place.
Repeated uploads create chaos
Every updated Excel file can mean new duplicates, missed changes and another round of manual checking.
Replace manual transfer with mapping, validation and import review.
Excel handover to Jira issues
From Excel workbook to reviewed Jira issues
This app was built for the moment when a team receives approved work in Excel and needs it in Jira. Instead of rebuilding the spreadsheet as CSV or copying each row by hand, use the workbook as the starting point and turn it into reviewed Jira issues.
Accepted offer to delivery work
Turn scoped rows, estimates and notes into Jira work items.
Discovery workshop output to Jira issues
Move structured workshop findings into Jira without rewriting them.
Client Excel handover to reviewed import
Validate incoming workbook data before it touches Jira.
Updated workbook to controlled update
Handle repeated uploads without losing track of existing issues.
Use the formal Excel handover as the starting point.
Who it helps
Who is Excel to Jira Importer and Updater for?
Use it when spreadsheet-based planning data needs to become reviewed Jira Cloud issues without fragile copy-paste or a custom CSV cleanup process.
Jira admins importing structured data
Set up controlled imports with mapped fields, validation and reports.
Project managers receiving backlog spreadsheets
Move reviewed scope, estimates and acceptance criteria into Jira.
Consultants migrating client workbooks into Jira
Turn client handover files into planned Jira issues with visible review steps.
Teams updating Jira issues in bulk from Excel
Use repeat uploads when spreadsheet changes need to update matching Jira issues.
Teams replacing fragile CSV cleanup workflows
Start from the workbook and clean values inside the import setup.
Atlassian partners helping clients move work into Jira
Use a Jira Cloud workflow that supports mapping, hierarchy planning and confirmation.
Use cases
Excel to Jira use cases
Import a client backlog from Excel to Jira
Map a client workbook into Jira issue fields and review the planned import before creating issues.
Update existing Jira issues from Excel
Use repeat imports to update selected fields on matching Jira issues when the setup supports stable row identity.
Convert Excel columns into structured Jira descriptions
Use Description Builder to combine acceptance criteria, notes and scope details into one Jira Description.
Import epics, stories and subtasks
Plan parent relationships and hierarchy when the workbook and Jira configuration support the desired structure.
Clean spreadsheet values before import
Normalize values before Jira validation so the import is based on cleaner mapped data.
Review all Jira changes before applying them
Check creates, updates, skipped rows and errors before Jira issues are changed.
Replace manual copy-paste from Excel into Jira
Move from row-by-row copying to a repeatable workflow with mapping, validation and reports.
How it works
How Excel to Jira Importer & Updater works
Upload the workbook
Use the Excel file you already have. No need to rebuild it as CSV first.
Choose worksheet and header row
Select the sheet and the row that contains column names.
Map Excel columns to Jira fields
Reuse mappings for repeated imports.
Build useful Jira descriptions
Combine business context, acceptance criteria, technical notes and estimates into a structured description.
Validate before import
Review required fields, value problems, hierarchy and duplicates before anything changes in Jira.
Create or update selected issues
Import only the rows you approve and keep an import report.
Description Builder turns scattered workbook context into a structured Jira Description.
Core capabilities
Everything you need for real Excel handovers
Direct Excel import
Upload XLSX, XLS or CSV files instead of rebuilding every workbook as a separate CSV template first.
Reusable setup
Save mappings and reuse them when similar files come back.
Description Builder
Build Jira descriptions from multiple Excel columns.
Value cleanup
Clean and normalize values before they become Jira field values.
Hierarchy from Excel
Preserve backlog structure when the source file contains hierarchy hints supported by the app's setup.
Issue links from Excel
Map issue link information when the workbook and Jira configuration support the intended relationship.
Validation before Jira changes
Review problems before creating or updating issues.
Duplicate handling
Reduce the risk of creating the same work again when the workbook returns.
Update existing issues
Use repeated imports to update selected Jira issues when the app can match previously imported rows.
Import report
See what was created, updated, skipped or failed after the import.
Product proof
Screenshots from the actual import workflow
Use the illustrations to understand the story, then check real product screens for the setup, validation and report flow.
Choose worksheet and header row
Start from the workbook structure
Select the sheet and header row before mapping Excel columns to Jira fields.
Description Builder
Build richer Jira descriptions
Combine multiple workbook columns into one structured Jira Description.
Validate before import
Review before Jira changes
Check row-level messages and selected rows before the final import action.
Import report
Keep evidence of the run
Review what was created, updated, skipped or failed after the import.
Safety
Nothing changes in Jira until you review and import
Uploading an Excel file is not the same as importing it. Use the app to configure mapping, validate rows and review the result before you create or update Jira issues. Jira changes happen only after the final import action.
Review rows before import
Import selected rows only
See validation problems before Jira changes
Keep a report after import
Security details are available before installation
Validation is the safety gate before selected Jira changes.
Excel to Jira vs Jira CSV import
Native Jira CSV import is useful for clean, prepared, admin-led imports. Excel to Jira Importer and Updater is better suited to real Excel workbooks, safer review, mapping, cleanup and repeatable workflows.
Use case
Native Jira CSV import
Excel to Jira Importer and Updater
Clean one-time CSV import
Good fit when the data is already prepared and an admin can run the import.
Possible, but usually more useful when the source is a workbook or repeat workflow.
Real Excel workbook with multiple sheets
Usually requires exporting or preparing a CSV file first.
Upload XLSX, XLS or CSV and choose the worksheet to import.
Header row not in the first row
Often requires spreadsheet cleanup before export.
Select the header row during setup.
Combining columns into Jira Description
Usually prepared manually in one CSV column.
Description Builder combines multiple Excel columns into a structured Jira Description.
Updating existing Jira issues
Possible with careful identifiers and admin-led preparation.
Designed for repeat uploads that update matching Jira issues when stable identity is available.
Previewing row-by-row changes
Part of the import process, but oriented around prepared CSV imports.
Review planned creates, updates, skipped rows and errors before Jira changes.
Importing hierarchy
Requires careful preparation of issue types, parent keys and import order.
Supports hierarchy setup where the workbook and Jira configuration allow the intended relationships.
Cleaning values before import
Usually handled before the CSV file is imported.
Use Value cleanup during setup before validation and import.
Repeatable mapping profiles
Depends on prepared templates and repeated admin setup.
Reusable setup helps recurring workbook imports keep the same mapping and cleanup choices.
Non-admin friendly workflow
Best suited to Jira administrators and prepared migration files.
Guided setup helps project users prepare imports, with installation handled through Jira admin approval when needed.
When a Jira CSV import error appears, start with a local explanation and a quick CSV preflight. These free browser tools do not require Jira access and do not send pasted import errors or selected files to an API.
CSV imports are possible, but fragile. Excel to Jira Importer & Updater lets you map real Excel workbooks, clean values, create or update Jira issues, and review every change before Jira is modified.
For non-admin users
Not a Jira admin? Send this to the person who can approve apps.
Many PMs, Scrum Masters and Business Analysts can see the problem but cannot install Marketplace apps themselves. Give them a clear next step instead of letting them bounce.
Send a clear trial request to your Jira administrator.
The app is designed as an Atlassian Forge app. It avoids storing full Excel files and stores only operational metadata needed for duplicate detection, saved mapping setup and reporting.
✓ Works with Jira Cloud and Jira REST APIs through Forge.✓ No separate vendor-hosted product backend for workbook data is described in current security documentation.✓ Read the security page, privacy policy and support page.
Founder credibility
Built by someone who has lived this handover problem
Excel to Jira Importer & Updater was built by a software delivery practitioner with 20 years of experience in software-house and consulting projects. The goal is simple: reduce the manual gap between formal Excel handovers and the Jira issues your team actually works from.
Excel to Jira Importer FAQ
Can Jira import Excel files directly?
Jira's native import flow is CSV-based. Excel to Jira Importer and Updater is for Jira Cloud teams that want to start from XLSX, XLS or CSV files and review mapped Jira changes before import.
How do I import Excel into Jira Cloud?
Upload the workbook, choose the worksheet and header row, map Excel columns to Jira fields, validate the rows, review planned creates or updates, then import only after confirmation.
Can I update existing Jira issues from Excel?
Yes. Repeat imports can update matching Jira issues when the import setup provides a stable identity such as a Jira issue key or another supported row identity. See the update Jira issues from Excel guide.
Can I import epics, stories and subtasks from Excel into Jira?
Yes, when the workbook structure and Jira configuration support the intended hierarchy. See the hierarchy import guide.
Do I need to convert Excel to CSV before importing to Jira?
No. The app can work from XLSX and XLS workbooks, and CSV is also supported for teams that already use CSV files.
Can I map Excel columns to Jira custom fields?
Yes. You can map workbook columns to Jira fields, including custom fields that are available in the selected Jira project and issue type configuration.
Can I combine multiple Excel columns into a Jira Description?
Yes. Description Builder can combine several Excel columns, such as business context, acceptance criteria and notes, into one structured Jira Description.
Can I review changes before Jira issues are created or updated?
Yes. Uploading and mapping the workbook does not change Jira immediately. You can validate rows and review planned creates, updates, skipped rows and errors before the final import.
Is this app for Jira Cloud?
Yes. Excel to Jira Importer and Updater is an Atlassian Marketplace app for Jira Cloud.
Does the app run on Atlassian?
The app is built for Atlassian Forge and Jira Cloud. See the security page and data processing summary for implementation and data handling details.
Is this an alternative to Jira CSV import?
It is an alternative workflow for real Excel workbooks, reusable mappings, value cleanup, row review and repeat imports. Native Jira CSV import can still be a good fit for clean one-time CSV files.
Can I use this for backlog migration from Excel to Jira?
Yes. The app can help migrate backlog spreadsheets into Jira Cloud when the workbook can be mapped to Jira fields and the planned hierarchy matches the target Jira configuration.
Turn your next Excel handover into reviewed Jira issues
Try it on the kind of workbook your team already receives: offer rows, scope notes, task lists, estimates, acceptance criteria and handover data.
