How to Bulk Upload Issues to Jira

Preparing your CSV file

The Jira Importers plugin assumes that your CSV file is based off a default Microsoft Excel-styled CSV file. Fields are separated by commas, and whatsoever content that must be treated literally, such as commas and new lines/'carriage returns' themselves are enclosed in quotes.

For Microsoft Excel and OpenOffice, it is not necessary to quote values in cells as these applications handle this automatically.

CSV file requirements

In addition to being 'well-formed', CSV files have the following requirements:

Each CSV file must possess a heading row with a Summary cavalcade

The CSV file import magician uses a CSV file's header row to determine how to map information from the CSV file's 2nd row and beyond to fields in your project'south problems.

The header rowshould avoid containing any punctuation (autonomously from the commas separating each cavalcade) or the importer may not work correctly.

The header rowmust incorporate a column for 'Summary' data.

Commas (as column/field separators) cannot be omitted

For example, this is valid:

            Summary, Assignee, Reporter, Issue Type, Description, Priority "Test result", admin, admin, i, ,

... simply this is not valid:

            Summary, Assignee, Reporter, Result Type, Clarification, Priority "Examination issue", admin, admin, ane

Encapsulating Jira information structure in your CSV file

Capturing data that spans multiple lines

Use double-quote marks (") in your CSV file to capture data that spans multiple lines. For instance, upon import, Jira will treat the following as a valid CSV file with a unmarried record:

            Summary, Description, Status "Login fails", "This is on a new line", Open

Treating special characters literally

Use double-quote marks (") around a department of text to care for whatever special characters in that department literally. In one case this data is imported, these special characters will exist stored every bit part of Jira'southward field data. Examples of special characters include carriage returns/enter characters (as shown in the example above), commas, etc.

To care for a double quote mark literally, you lot can 'escape' them with another double quote mark graphic symbol. Hence, the CSV value:

"Clicking the ""Add together"" push results in a page not found mistake"
once imported, volition be stored in Jira every bit:
Clicking the "Add" button results in a page non plant error

Aggregating multiple values into single issue fields

Yous can import multiple values into an issue field that accepts multiple values (due east.g.Fix (for) Version,Affects Version,Component,Labels). To do this, your CSV file must specify the same column name for each value you lot wish to aggregate into the mapped issue field. The number of column names specified must match the maximum number of values to exist aggregated into the mapped field. For example:

            IssueType, Summary, FixVersion, FixVersion, FixVersion, Component, Component problems, "First event", v1, , , Component1, issues, "Second effect", v2, , , Component1, Component2 bug, "Third issue", v1, v2, v3, Component1,

In the to a higher place example, theComponent field of the second issue and thePrepare Version field of the third outcome will generate multiple values in appropriate issue fields upon import.

Be aware that simply a limited number of event fields support multiple values. The CSV importer volition not permit you to import aggregated data into issue fields that only support a unmarried value.

Importing issues into multiple projects

Y'all tin import issues from your CSV file into unlike projects through a CSV file import. To do this:

Your CSV file requires two boosted columns whose headings should exist named similarly toProjection Proper noun andProjection Key.
Ensure that every issue represented in your CSV file contains the appropriate proper name and key in these columns for the projects to which they will be imported.
The project name and key information is theminimum project data required for importing problems from a CSV file into specific projects.

            IssueType, Summary, Projection Proper noun, Project Key issues, "First outcome", Sample, SAMP problems, "2d issue", Sample, SAMP task, "Third upshot", Example, EXAM

In the example above, the first and second issues will be imported into the 'Sample' project (with project key 'SAMP') and the 3rd issue will be imported into the 'Instance' project (with projection key 'EXAM') , bold you lot friction match the 'Projection Name' and 'Project Key' fields in your CSV file to theProject name andProject key issue fields, respectively during the CSV file import wizard.

Importing work log entries

Your CSV file can contain work log entries. For example:

            Summary,Worklog Only time spent (1 hour),3600 With a date and an author,2012-02-x 12:30:10;wseliga;120 With an additional annotate,Testing took me three days;2012-02-10 12:thirty:10;wseliga;259200

To track time spent, you need to use seconds.

Importing to multi select custom fields

Your CSV file can contain multiple entries for the one Multi Select Custom Field. For example:

            Summary,Multi Select,Multi Select,Multi Select Sample issue,Value one,Value ii,Value three

This will populate the Multi Select Custom Field with multiple values.

Importing cascading choice custom fields

You lot tin import values to a cascading choice custom field using the following syntax:

            Summary, My Cascading Custom Field Example Summary, Parent Value -> Kid Value

The '->' separator allows y'all to import the hierarchy.

NOTE: Currently Jira does not support importing multi-level cascading select fields via CSV ( JRA-34202 - Getting issue details... STATUS ).

Running the CSV file import sorcerer

Before you begin: If your Jira installation has existing data, you should back it up.

SelectIssues > Import Issues from CSVto open up theMajority Create Setup folio. (If you lot do not have the pickImport problems from CSV, your Jira Admin must update the Jira Importers plugin to version 6.ii.iii or to a higher place.)
On theSetup folio, select yourCSV Source File.
Go out theUse an existing configuration file checkbox cleared if you practice not have a configuration file, or if you want to create a new configuration file. Configuration files specify a mapping between column names in your CSV file'due south header row and fields in your installation.
- If you select this selection, you volition be asked to specify anExisting Configuration File.
- If you do not select this option, then at the cease of the CSV file import wizard, Jira will inquire you if you lot want create a configuration file that you can use for subsequent CSV imports.
Click theNext button to continue to theSettings footstep of the CSV file import wizard. Complete the required fields.
- If your CSV file uses a dissimilar separator character other than a comma, specify that character in theCSV Delimiter field. If the separator is a 'Tab', this tin exist entered using the format '/t'.
Click theNext button to proceed to theMap fields step of the CSV file import wizard. Here, you lot tin can map the column headers of your CSV file to the fields in your selected projection. If you want to select specific Jira field values to map specific CSV values to, tick the checkbox forMap field value.
Note:You must map a CSV field to the issue'due south summary field. This ensures the problems created accept a summary.
Click theNext push button to proceed to theMap values step of the CSV file import wizard. On this stride of the import wizard, you can select which specific CSV field values you lot want to map to which specific issue field value. For example, your outcome types you may have a CSV field value of "Feature Request", which you may desire to map to the issue type field value "New Feature".
Please note:
- Any fields whoseMap field value checkboxes were selected in the previous step of the CSV file import wizard will be presented on this page.
- Leave a field cleared or clear any content within it if you wish to import the value 'equally is'.
- If you are importing a username-based CSV field (e.g.Reporter orAssignee) and you lot do not select theMap field value checkbox for this field in the previous step of the CSV file import wizard, then the importer volition automatically map imported usernames from the CSV file to (lowercase) Jira usernames.
  Regardless of whether or not you select theMap field value checkbox, Jira will automatically create usernames based on the data in your CSV file if they have non already been defined in Jira.
- When importing descriptions with line breaks, practise not select theMap field value checkbox equally Jira might then remove the line breaks.
Click theBegin Import button when you are fix to begin importing your CSV data into Jira. The importer will display updates as the import progresses, so a success bulletin when the import is complete.
If you're confident your import is correctly ready, click theBegin Import push button. Your import volition begin and in one case complete you will be informed of whatever errors. If you'd like to check your import first, click theValidate push and Jira will validate your import and inform you of any expected errors or warnings. You lot can then go dorsum and correct these before running your full import.

Annotation:

- If you experience problems with the import (or you are curious), click thedownload a detailed log link to reveal detailed information most the CSV file import procedure.
- If you need to import another CSV file with the same (or similar) settings to what you used through this procedure, click thesave the configuration link to download a CSV configuration file, which y'all tin apply at the first step of the CSV file import sorcerer.

Congratulations, you lot accept successfully imported your CSV information into Jira! If you have any questions or meet whatsoever bug, please contact Atlassian support.

Tips for importing CSV data into outcome fields

Below are some helpful tips when importing data from your CSV file into specific effect fields:

Event Field	Import Notes
Project	CSV information is imported on a per-projection basis. You can either specify an existing project(due south) as the target, or the importer will automatically create a new project(southward) for you at fourth dimension of import.
Summary	This is the merely required field.
Component(south)	You tin can import issues with multiple components past entering each component in a separate column.
Affects Version(s)	You can import problems with multiple 'Affects Versions' past entering each version in a separate cavalcade.
Fix Version(s)	You can import issues with multiple 'Fix Versions' by inbound each version in a separate column.
Due Date	Please use the date format specified on the second step of the CSV import magician.
Issue Type	If not specified in your CSV file, imported bug will be given the default (i.e. starting time) Issue Type, as specified in your Jira instance. For more than information, see Defining issue blazon field values. You lot can also create new values on-the-fly during the import process.
Labels	Import issues with multiple labels by: entering each characterization in a carve up column or putting all labels in one column, deliminated by a space
Priority	If not specified in your CSV file, imported issues volition exist given the default (i.e. showtime) Priority as specified in your Jira instance. For more information, see Defining priority field values. You lot can also create new values on-the-fly during the import process.
Original Estimate	The value of this field needs to be specified every bit number of seconds.
Remaining Estimate	The value of this field needs to exist specified as number of seconds.
Users	You can choose to have the importer automatically create Jira users for any values of the Assignee or Reporter field. Users will be created every bit agile accounts in Jira. Users will need to become their passwords emailed to them the first time they log into Jira. Users with no real name volition get the portion of their email address (login name) before the "@" graphic symbol equally their Full Name in Jira. If you are using External User Management, the import process will not be able to create users; instead, the importer volition give you a listing of any new users that need to be created. Yous will need to create the users in your external user repository before commencing the import. If you have a user-limited license (e.g. personal license), and the number of required users is larger than the limit, then the import volition be stopped. A page volition be displayed showing a list of users that tin't be created. If Assignee and Reporter are not mapped, and so no usernames are created.
Other fields	If you lot wish to import whatever other fields, you can choose to map them to specific Jira custom field(s). If your custom fields don't be yet in Jira, the importer can automatically create them for you. If your custom field is a engagement field, please use the date format specified on the 2nd step of the CSV import wizard.

Known issues

Problems populating multi-select fields

In case your bug get created only the multi-select fields are not populated, contact your administrator then that they tin re-run the import using Jira admin tools.

Bright Suicklentrot1972