Map Excel columns to Jira fields before importing
Field mapping is where a spreadsheet becomes a planned Jira change. You decide which Excel columns should fill Jira fields, which columns should stay as review context and which values need cleanup before validation.
Why mapping matters
Mapping is a safety boundary. Excel may contain useful notes, temporary calculations and client labels, but not every column should become a Jira field value. A deliberate mapping keeps the import focused and makes updates easier to review.
Standard Jira fields
Common fields include Summary, Issue Type, Description, Priority, Assignee, Reporter, Due date, Labels, Components and Story Points. Required fields depend on the selected Jira project and issue type configuration, so validation should happen after mapping.
Custom fields
The app can map workbook columns to custom fields available in the selected Jira project and issue type configuration. Use custom fields for data the team will actually maintain in Jira. If a column is mostly context, Description Builder may be a cleaner choice than creating more custom fields.
User, date and priority values
User fields should contain values Jira can resolve, such as emails, display names or account IDs depending on the field behavior. Date values should use a format that validates consistently. Priority values should match Jira priorities, or be cleaned before import when the workbook uses labels such as P1, urgent or must-have.
| Excel value | Jira target | Mapping note |
|---|---|---|
| Owner Email | Assignee | Validate users before import. |
| Target Date | Due date | Normalize ambiguous dates before validation. |
| P1 | Priority | Use cleanup or value mapping if Jira expects Highest. |
| Acceptance Criteria | Description Builder | Combine with context and notes into one readable description. |
Description Builder: combine multiple Excel columns into a structured Jira description
Jira Description often needs more than one workbook column. Description Builder can combine business context, acceptance criteria, implementation notes and source references into one structured Jira Description.
Save and reuse mapping profiles
Saved setup helps when a similar workbook returns later. Review it every time: columns can be renamed, removed or reused for a different meaning. A reused mapping should speed up setup, not replace human review.
Related guides
Map fields before Jira changes
Use the product workflow to turn workbook columns into reviewed Jira values.