Get started with Jira Work Management
New to Jira Work Management? Check out our guides for new administrators and users.
When you map data in Jira Work Management, you can connect the information in your import columns to the issue fields in your project. This allows you to customize how the data is presented and organized. For instance, you can map the dates from your CSV file to the "Start date" or "End date" for an issue on your business project.
To map your data, simply preview the CSV import columns and adjust the data mapping in the preview screen before creating your project. This gives you the flexibility to tailor your project to your specific needs and ensure that your data is accurate and relevant.
After uploading your CSV file, you’ll see a dynamic preview table for the first 30 rows of data in your CSV.
This table is where you can map the column data to fields for how you want them to appear in the business project. We’ll create an issue in your new Jira Work Management project for each row of data.
The first row of the table is where you can map your data, and the second row of the table is where you can see the headers for the data from your CSV file.
Most of the data from your file will be mapped automatically based on your column’s name and existing Jira field names. You’ll need to double-check the columns are mapped correctly.
To map data to a field, select Map to a field in the first row of the preview table.
From the dropdown select the field type that best maps to the data of that column. From the dropdown, you can choose to exclude data from your import, create a custom field for specific information, or map data to Jira fields or previously created custom fields.
Note: At least one of the mapped fields must contain data for the issue’s summary field.
Columns that aren’t mapped will be automatically excluded from the import.
To import date and time data in Jira, adjust the date and time format options to match the CSV file and specify the date format used in the file using Java SimpleDateFormat syntax. Jira will read the dates and times based on the language and region preferences set in the CSV.
Use custom fields in Jira Work Management to track and manage additional information specific to your team or organization's needs.
Jira provides a set of standard fields that can be used for most purposes, but custom fields allow you to capture and report on data that is unique to your workflow or business processes. Custom fields can be created for various types of data, such as text, numbers, dates, and dropdown lists, and can be added to screens, issue types, and projects as needed. With custom fields, you can enhance your instance's flexibility and tailor it to your team's requirements, improving data accuracy and helping you make informed decisions. Learn more about custom fields
Limit the number of custom fields in your import.
Avoid duplicating names of existing custom fields or standard Jira fields
Use generic names for custom fields that can be reused in other places e.g. Objective instead of Marketing Objective
Select Map to a field in your preview table for the column where you want to create a custom field.
From the dropdown select Create a custom field, then select the field type that best fits with your column field.
Your CSV file can contain multiple entries for the one Multi Select Custom Field. For example:
1
2
Summary,Multi Select,Multi Select,Multi Select
Sample issue,Value 1,Value 2,Value 3
This will populate the Multi Select Custom Field with multiple values.
You can import values to a cascading choice custom field using the following syntax:
1
2
Summary, My Cascading Custom Field
Example Summary, Parent Value -> Child Value
The '->' separator allows you to import the hierarchy.
If you come across unwanted or irrelevant data during the import process in the preview screen, you have the option to exclude the corresponding column from the import.
Select Exclude column data from your import from the field mapping dropdown to exclude data columns.
Once columns have been deliberately excluded from the dropdown you’ll also see that from the columns dropdown above your preview table. If you accidentally exclude a column that you want to bring back into the import, simply select the column heading from the dropdown again.
The following are some helpful tips along with a list of the system fields and custom fields that we currently support in Jira Work Management import.
System Fields | Description |
---|---|
SUMMARY | Maps to Jira Summary field type. Supports any text content. |
DESCRIPTION | Maps to Jira Description field type. Supports any text content. |
ENVIRONMENT | Maps to Jira Environment field type. Supports any text content. |
ISSUE_TYPE | Maps to Jira Issue Type field type. Supports any text content. e.g Task, Bug, Story |
STATUS | Maps to Jira Status field type. Supports any text content. e.g. To Do, In Progress, Done |
PRIORITY | Maps to Jira Priority field type. Supports any text content. |
DUE_DATE | Maps to Jira Date field type. Supports any date without the time. e.g. 11/03/2023 |
LABELS | Maps to Jira Labels field type. Supports any text content. |
COMMENT | Maps to Jira Comment field type. Supports any text content along with author and date. e.g date-time;author;body |
STATUS_CATEGORY | Maps to Jira Status category field type. Supports any string content. e.g ToDo, IN_Progress, Done |
CREATED | Maps to Jira Date time field type. Supports any date and time. e.g. 11/03/2023 11:53pm |
UPDATED | Maps to Jira Date time field type. Supports any date and time. e.g. 11/03/2023 11:53pm |
CREATOR | Maps to Jira User field type. Support any user Atalassian account Id. |
REPORTER | Maps to Jira User field type. Support any user Atalassian account Id. |
ASSIGNEE | Maps to Jira User field type. Support any user Atalassian account Id. |
WATCHES | Maps to Jira Watches field type. Support any multi user fields format. |
WORKLOG | Maps to Jira WorkLog field type. Supports these format -
|
TIME_ORIGINAL_ESTIMATE | Maps to Jira Time Orignal Estimate. Supports any integer values in sec. e.g 12 |
TIME_REMAINING_ESTIMATE | Maps to Jira Time Remaining Estimate. Supports any integer values in sec. e.g 12 |
TIME_SPENT | Maps to Jira Time Time Spent. Supports any integer values in sec. e.g 12 |
Custom fields | Description |
---|---|
Text Fields | Maps to Jira Text field type. Supports any text content. |
Paragraph | Maps to Jira Text Area field type. Supports any text content. |
Date | Maps to Jira Date field type. Supports any date without the time. e.g. 11/03/2023 |
TimeStamp | Maps to Jira Date time field type. Supports any date and time. e.g. 11/03/2023 11:53pm |
Number | Maps to Jira Number field type. Supports any valid number. e.g. 1234 |
Labels | Maps to Jira Label field type. Supports any valid string. For multiple labels, make sure to follow the multi select format where there is a column for each label |
DropDown | Maps to Jira Select field type. Supports any valid string and will create an option for all unique values in the column. |
Multi Select | Maps to Jira Multi Select field type. make sure to follow the multi select format below where there is a column for each value in the csv. |
Select List | Maps to Jira cascading select field type. Supports parent -> child format |
Multi User Picker | Maps to Jira multi user field type. To support multiple users, make sure to follow the multi select format below where there is a column for each user in the csv. Make sure the value is either an Atlassian account Id or email |
User Picker | Maps to Jira user field type. Make sure the value is an email |
CheckBox | Maps to Jira multi checkbox field type. Make sure it follows the multi select format below where there is a column for each value of the field. |
Url | Maps to Jira Url Field type. Make sure value is a valid url |
Radio | Maps to Jira Radio Button field type. Supports any valid string and will create an option for all unique values in the column. |
Jira Work Management has character limits for certain fields. Any data that exceeds the limit will be trimmed and excluded from the import. By keeping these character limits in mind when importing data into Jira Work Management, you can ensure that your information is accurately and completely represented in your project.
The following are the character counts for each field type.
Jira Fields | Character limit |
---|---|
Summary | 255 |
Description, Environment | 30k |
Issue Type | 60 |
Issue Status | 60 |
Priority | 60 |
Resolution | 60 |
Labels | 255 |
Text Field | 255 |
Text Area | 30k |
Custom Fields | 255 |
Was this helpful?