Does the app change Jira before review?
No. Jira changes happen only after validation, review and confirmation.
Review Jira creates and updates before you import
Bulk imports should not be blind. Excel to Jira Importer and Updater separates workbook setup from Jira changes so teams can validate rows, inspect planned creates and updates, select what to import and confirm only when the review makes sense.
Bulk imports should not be blind
A workbook can contain stale rows, missing required values, invalid users, duplicate items, unsupported parent relationships or fields that should not overwrite existing Jira issues. Review gives the team a chance to catch those issues before data is written to Jira.
See what will be created, updated, skipped or rejected
The review should make row status visible. Create candidates, update candidates, skipped rows and errors deserve different decisions. A row that cannot be matched should not quietly update the wrong issue, and a row with invalid values should be fixed before confirmation.
Compare Excel rows with Jira fields
Review final Jira values, not just source spreadsheet cells. This matters when mapping, cleanup, Description Builder or hierarchy setup changes how workbook values will be sent to Jira.
| Review area | What to check | Why it matters |
|---|---|---|
| Required fields | Summary, issue type and project-required custom fields | Missing values block import. |
| User fields | Assignee, Reporter and multi-user fields | Invalid users cause row errors. |
| Updates | Matched issue key and fields to be changed | Prevents accidental overwrites. |
| Hierarchy | Parent keys, generated paths and skipped duplicates | Keeps work under the intended parent. |
Select what to import
Review is also a control point. If only some rows are ready, import only approved rows and leave problem rows out until the workbook or mapping is corrected.
Nothing changes in Jira until confirmation
Uploading a workbook, selecting a worksheet, mapping fields and validating rows do not create or update Jira issues. Jira changes happen after the final import action, once the user has reviewed the result.
Related guides
Update Jira issues from ExcelUnderstand review risk for existing Jira issues.Field mappingControl what workbook values become Jira values.Hierarchy importReview parent-child relationships before creation.CSV vs ExcelCompare native CSV import with workbook review.
FAQ
Can I select which rows to import?
Yes. Review helps users inspect rows and import only approved rows.
Use review as the safety checkpoint
Test the workflow with a representative workbook and check the planned Jira changes before confirming.