How to import to jira
How to import to jira
How to import to jira
Discover Jira Cloud products
Learn more about Jira Cloud products, features, plans, and migration.
Integrate Jira Cloud with other products and apps
Integrate Jira Cloud with Confluence, development tools, apps, and self-hosted tools using OAuth and feature flags.
Manage users, groups, permissions, and roles in Jira Cloud
Control who has access to your Jira Cloud products and give them the right permissions to perform their role.
Configure and manage projects to track team progress
Learn how to set up, customize, and manage Jira Cloud projects.
Configure issues to track individual pieces of work
Explore issues, issue types, issue custom fields, issue screens, custom field context, and issue field configurations in Jira Cloud.
Create and manage issue workflows and issue workflow schemes
Define the lifecycle of your work and learn about issue workflow schemes and the issue collector.
Learn more on how you can set up Jira Cloud for your team.
Create issues using the CSV importer
Comma-separated value (CSV) files are text files that represent tabulated data, and are supported by most systems that handle tabulated data, such as spreadsheets and databases. The CSV importer allows you to import data from external systems that can export their data in a tabulated format. It also allows you to create your own CSV file to perform bulk issue creation and updates.
You will need the Create Issue project permission and the Make bulk changes global permission for the projects you want to create issues in. Note that your administrator can perform more advanced bulk imports. If you’re an administrator, check out Importing and exporting data for more information.
Preparing your CSV file
You can base the structure of your CSV file off the default Microsoft Excel CSV format. Fields should be separated by commas, and any content that must be treated literally (such as commas, new lines, and carriage returns) should be enclosed in quotes. Please note that Microsoft Excel and OpenOffice automatically quote values in cells, so there is no need to quote these values manually.
CSV file requirements:
This is a valid example:
This is not a valid example:
How to structure data in your CSV file
Data that spans multiple lines
Use double-quote marks ( » ) in your CSV file to capture data that spans multiple lines. For example, upon import, Jira will treat the following as a valid CSV file with a single record:
Special characters that need to be treated literally
Use double-quote marks ( » ) around a section of text to treat any special characters in that section literally. Once this data is imported, these special characters will be stored as part of Jira’s field data. Examples of special characters include carriage returns/enter characters (as shown in the example above), commas, etc.
To treat a double quote mark literally, you can ‘escape’ them with another double quote mark character. Hence, the CSV value:
Multiple values that need to be aggregated into single issue fields
You can import multiple values into an issue field that accepts multiple values (e.g. Fix (for) Version, Affects Version, Component, Labels). To do this, your CSV file must specify the same column name for each value you wish to aggregate into the mapped issue field. The number of column names specified must match the maximum number of values to be aggregated into the mapped field. For example:
In the above example, the Component field of the second issue and the Fix Version field of the third issue will generate multiple values in appropriate issue fields upon import.
Please be aware that only a limited number of issue fields support multiple values. The CSV importer will not allow you to import aggregated data into issue fields that only support a single value.
Attachments
You can attach files to issues created from your CSV file. To do this, specify the URL of your attachment in an ‘Attachments’ column within your CSV file.
URLs for attachments support the HTTP and HTTPS protocols and can be any location that your Jira instance must be able to access.
Issues that need to be imported to multiple projects
You can import issues from your CSV file into different projects through a CSV file import. To do this, add two columns to your CSV file with the «Project Name» and «Project Key» headings.
Make sure that every issue in your CSV file has a project name and project key in the relevant column. The project name and project key are the minimum project data required for importing issues from a CSV file into specific projects.
In the following example, the first and second issues will be imported into the ‘Sample’ project (with project key ‘SAMP’), while the third issue will be imported into the ‘Example’ project (with project key ‘EXAM’):
Work log entries
Your CSV file can contain work log entries. Use seconds to track time spent. For example:
Multi-select custom fields
Your CSV file can contain multiple entries to populate the Multi Select Custom Field with multiple values. For example:
Cascading choice custom fields
You can import values to a cascading choice custom field using the following syntax. The ‘->’ separator allows you to import the hierarchy:
Running the CSV file import wizard
Click Next and map the column headers of your CSV file to the fields in your selected project. If you want to select specific Jira field values to map specific CSV values to, check the Map field value option. You must map a CSV field to the issue summary field, as all issues created must have a summary.
Click Next one more time and select which CSV field values selected in the previous step you want to map to specific issue field values. For example, you might want to map the CSV field value of «Feature Request» to the Jira issue type field value «New Feature».
Tips for importing CSV data into issue fields
Below are some helpful tips when importing data from your CSV file into specific issue fields:
CSV data is imported on a per-project basis. You can either specify an existing project(s) as the target, or the importer will automatically create a new project(s) for you at time of import.
This is the only required field.
You can import issues with multiple components by entering each component in a separate column.
You can import issues with multiple ‘Affects Versions’ by entering each version in a separate column.
You can import issues with multiple ‘Fix Versions’ by entering each version in a separate column.
You can import issues with multiple comments by entering each comment in a separate column.
Please use the date format specified on the second step of the CSV import wizard.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Issue Type, as specified in your Jira instance. For more information, see Defining issue type field values.
You can also create new values on-the-fly during the import process.
You can import issues with multiple labels by entering each label in a separate column.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Priority as specified in your Jira instance.
You can also create new values on-the-fly during the import process.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
Creating users
For any system field that is a user type, we support:
Atlassian Account ID
You can choose to have the importer automatically create Jira users for any values of the Assignee or Reporter field.
Updating users
Portal-only customer data in Jira Service Management behaves differently than other user accounts data. If the portal-only customer data is different in the import and the destination, then we use the destination data.
When importing to projects with mandatory fields, you must include the field in the *Create issue* screen associated to the issue type being used. For more information, see Specifying field behavior.
If you wish to import any other fields, you can choose to map them to specific Jira custom field(s). If your custom fields don’t exist yet in Jira, the importer can automatically create them for you. If your custom field is a date field, please use the date format specified on the second step of the CSV import wizard.
You can’t import Select List (cascading) custom field types using this method. Instead, select Settings ( 
) > System > External System Import to import Select List (cascading) fields.
If you have any questions or encounter any problems during the CSV import process, please contact Atlassian support.
Import issues
You can import issues into your Jira Cloud site. We recommend using this process to import data from third-party tools.
Import overwrites existing data
This import process overwrites existing data and configuration (including cross-application settings) in your Jira cloud site. This impacts existing issues and attachments, and look and feel configuration.
You can choose to also overwrite all users or to merge users from the import file into the existing cloud userbase. Be aware that this can cause permission escalation. Find out more about migrating Jira from server to cloud.
The exception is portal-only customer accounts in Jira Service Management. If the portal-only customer data is different in the import and the destination site, then we use the destination version.
Generate a backup file
From another Jira Cloud site
Follow the steps on Exporting issues to generate a backup file. Then read the import steps below.
From a Jira Server instance
Follow the steps on Backing up data to generate a backup.
If your Jira Server version is 7.6.0 or higher, you don’t need to upgrade before migrating.
If your Jira Server version is between 7.0.0 and 7.6.0 (released November 2017) we recommend upgrading to 7.6.0 or higher before migrating. Migrating versions between 7.0.0 and 7.6.0 may work, but these versions are no longer guaranteed to work without requiring an upgrade.
If your Jira Server version is below 7.0.0 (released October 2015) you need to upgrade to 7.6.0 or higher before migrating. To help you migrate, check out Upgrading Jira applications.
From other tools
Check out Migrating from other tools to find out more about importing data from CSV and JSON.
Import a backup file
Importing entities.xml and activeobjects.xml will overwrite the database in your Jira Cloud site. Importing the attachments, avatars, or logos files will overwrite any existing attachments, avatars, or logos in your Jira Cloud site, respectively.
Before you import, unzip the backup file and make sure it has a file structure similar to:
If you’ve unzipped and edited an export from a Jira Cloud site, and are re-zipping it on a Mac, the process may add hidden files that will cause the import to fail. To ensure there are no hidden files, run these commands in Terminal (where filename.zip is the name of the file you’re going to import):
To import your backup file:
> System
Under IMPORT AND EXPORT, click Restore system and follow the steps.
After the import
Granting application access to new users
The import process does not honor the default application access settings and does not give access to any applications to new users. You must grant application access to these users for them to be able to log in.
For information on how to assign application access, see Update product access settings.
Setting permissions
This process imports global permission settings such as Browse users and groups; however, imports from Jira Server to Jira Cloud will not contain the Jira System Administrators global permission (which doesn’t exist in Jira Cloud) and will not contain any changes made to the Administer Jira global permission.
Administering Jira applications Support
Products
Jira Software
Project and issue tracking
Jira Service Management
Service management and customer support
Jira Core
Manage any business project
Confluence
Bitbucket
Git code management
Resources
Documentation
Usage and admin help
Community
Answers, support, and inspiration
Suggestions and bugs
Feature suggestions and bug reports
Marketplace
Billing and licensing
Frequently asked questions
Viewport
Confluence
Versions
Importing data from CSV
Migrating from other issue trackers
On this page
In this section
Related content
Still need help?
The Atlassian Community is here for you.
The Jira Importers plugin, which is bundled with Jira, allows you to import your data from a comma-separated value (CSV) file. This might be helpful when you are migrating from an external issue tracker to Jira.
CSV files are text files representing tabulated data and are supported by most applications that handle tabulated data (for example, Microsoft Excel, databases, etc.).
The CSV import feature allows you to import issues from an external (issue tracking) system that can export its data in a structured or tabulated format (preferably CSV).
Our main website highlights some top reasons why people migrate from such an external issue tracking system to Jira.
The CSV import process consists of the following stages:
Several methods are available for importing data from other issue tracking systems into Jira. Depending on your other issue tracking system, it may be more appropriate to use a different import method instead of exporting data from that system to a CSV file and then importing that CSV file to Jira.
If your other issue tracking system is listed on the Migrating from other issue trackers page, try using the appropriate method to import data to Jira.
You may also want to use the Bulk issues import feature instead of External system import. Learn more about Bulk issues import in here.
On this page:
Preparing your CSV file
The Jira Importers plugin assumes that your CSV file is based off a default Microsoft Excel-styled CSV file:
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 column
The CSV file import wizard (see more details below) uses a CSV file’s header row to determine how to map data from the CSV file’s 2nd row and beyond to fields in Jira.
The header row shouldn’t contain any punctuation, except for the commas separating each column. Otherwise, the importer may not work correctly.
The header row must contain a column for the issue’s «Summary» data.
Commas (as column/field separators) cannot be omitted
For example, the following format is valid:
While this one is not valid:
Encapsulating Jira data structure in your CSV file
In this section, youβll find solutions for the following issues:
Capturing data that spans multiple lines
Use double-quote marks ( » ) in your CSV file to capture data that spans multiple lines. For example, during import, Jira will treat the following as a valid CSV file with a single record:
Treating special characters literally
Use double-quote marks ( » ) around a section of text to treat any special characters in that section literally. Once this data is imported into Jira, these special characters will be stored as part of Jira’s field data. Examples of special characters include carriage returns/enter characters, commas, etc.
To treat a double quote mark literally, you can «escape» them with another double quote mark character. For example:
Aggregating multiple values into single Jira fields
You can import multiple values into a Jira field that accepts multiple values. For example, Fix (for) Version, Affects Version, Component, or Labels. To do this, your CSV file must specify the same column name for each value you wish to aggregate into the mapped Jira field. The number of column names specified must match the maximum number of values to be aggregated into the mapped field. For example:
In this example, the Component field of the second issue and the Fix Version field of the third issue will generate multiple values in appropriate Jira fields upon import.
Be aware that only a limited number of Jira fields support multiple values. The CSV importer will not allow you to import aggregated data into Jira fields that only support a single value.
Importing attachments
You can attach files to issues, created from your CSV file. To do this, specify the URL of your attachment in an «Attachments» column in your CSV file.
URLs for attachments support the HTTP and HTTPS protocols and can be any location that your Jira server must be able to access. You can also use the FILE protocol to access files in the import/attachments subdirectory of your Jira home directory.
Creating sub-tasks
You can create sub-tasks of issues through a CSV file import by encapsulating this structure in your CSV file. To do this:
In this example, the fourth issue will be imported as a sub-task of the second issue, assuming you match the «Issue ID» and «Parent ID» fields in your CSV file to the Issue Id and Parent Id Jira fields respectively during the CSV file import wizard.
Importing issues into multiple Jira projects
You can import issues from your CSV file into different Jira projects through a CSV file import. To do this:
Ensure that every issue represented in your CSV file contains the appropriate name and key in those columns for the Jira projects to which they will be imported.
The project name and key data is the minimum Jira project data required for importing issues from a CSV file into specific Jira projects.
Handle unresolved issues
For fields mapping to Resolution, Priority, and Issue Type, you will get a select list with the available values in Jira. In addition, you can quickly create values that do not exist in Jira by clicking the green plus symbols.
For fields mapping to Status, you will get the select list with Jira’s available values, but no plus symbol for creating new status values.
For these four fields, there are two special options in the select list in addition to Jira’s available values:
Importing worklog entries
Your CSV file can contain worklog entries. For example:
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:
This will populate the Multi Select Custom Field with multiple values.
Importing cascading choice custom fields
You can import values to a cascading choice custom field using the following syntax:
The ‘->’ separator allows you to import the hierarchy.
Updating existing issues
From version 4.3 of Jira Importers plugin, you can update existing issues. Your CSV file needs to contain a column that will be mapped to Issue Key during the import. If an issue exists for a given key, it will be updated. For example:
The first row will create an issue, the second row will set votes to 7 and add two labels. The following row will change the summary. Issue TT-2 will be created with two labels, but the second row will remove those labels with a special marker >.
Importing a CSV to update existing issues will reset columns to their default values if they are not specified in the CSV.
Running the CSV file import wizard
Before you begin, you need to back up your Jira data.
On the CSV File import page, select your CSV Source File. If you want to change the file’s encoding and CSV delimiter format, select the Advanced heading to reveal this option.
Leave the Use an existing configuration file checkbox cleared if you do 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’s header row and fields in your Jira installation.
On the Setup project mappings page, you can either import all your issues into either one Jira project (new or existing), or multiple Jira projects. If you choose to import to multiple projects, ensure that your CSV file includes the minimum Jira project data required, which is Jira project name and key. Complete the following fields/options:
Choose one of the following:
Enter the project Key
This will be used as the prefix for all issue IDs in your Jira project.
Check that the key of the project where youβre importing issues is the same as the issue key. Otherwise, Jira will import issues to the project but give them new issue keys.
Select Next to proceed to the Setup field mappings step of the CSV file import wizard.
In the Setup field mappings page, map the fields in the CSV file to the issue fields in the selected project. In the Jira field column, select the Jira field that you want to map to the field from the CSV file. For more information about matching CSV fields to Jira fields, see Tips for importing CSV data into Jira fields below.
For CSV fields that have been aggregated by the CSV file import wizard, you will only be able to select Jira Fields that support multiple values.
On the Setup value mappings page, specify the Jira field values for each CSV file field value that has been detected by the CSV file import wizard.
Leave a field cleared or clear any content within it if you wish to import the value «as is».
You can create new Priority, Resolution, and Issue Type values in Jira (i.e. based on the data in your CSV file) by selecting the Add new link next to the appropriate field.
If you are importing a username-based CSV field (e.g. Reporter or Assignee) and you didn’t select the Map field value checkbox for this field in the previous step of the CSV file import wizard, then the importer will automatically map imported usernames from the CSV file to (lowercase) Jira usernames.
Regardless of whether or not you select the Map field value checkbox, Jira will automatically create usernames based on the data in your CSV file if they haven’t been defined in Jira yet.
Select the Begin Import button when you are ready to begin importing your CSV data into Jira. The importer will display updates as the import progresses, then a success message when the import is complete.
Congratulations, you have successfully imported your CSV data into Jira! If you have any questions or encounter any problems, please contact Atlassian support.
Tips for importing CSV data into Jira fields
The following are some helpful tips when importing data from your CSV file into specific Jira fields.
CSV data is imported on a per-project basis. You can either specify an existing Jira project(s) as the target or the importer will automatically create a new project(s) for you at time of import.
This is the only required field.
You can import issues with multiple components by entering each component in a separate column.
You can import issues with multiple ‘Affects Versions’ by entering each version in a separate column.
You can import issues with multiple ‘Fix Versions’ by entering each version in a separate column.
You can import issues with multiple comments by entering each comment in a separate column.
Please use the date format specified on the second step of the CSV import wizard.
Please use the date format specified on the second step of the CSV import wizard.
Please use the date format specified on the second step of the CSV import wizard.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Issue Type as specified in your Jira system Defining issue type field values. You can also create new Jira values on-the-fly during the import process.
Import issues with multiple labels by:
If not specified in your CSV file, imported issues will be given the default (i.e. first) Priority as specified in your Jira system Defining priority field values. You can also create new Jira values on-the-fly during the import process.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Resolution as specified in your Jira system Defining resolution field values. You can also create new Jira values on-the-fly during the import process.
Can only be mapped to existing workflow statuses in Jira. If not specified in your CSV file, imported issues will be given the default (i.e. first) Status as specified in your Jira system.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
You can choose to have the importer automatically create Jira users for any values of the Assignee or Reporter field.
If you wish to import any other fields, you can choose to map them to specific Jira custom field(s). If your custom fields don’t yet exist in Jira, the importer can automatically create them for you. If your custom field is a date field, please use the date format specified on the second step of the CSV import wizard.
Importing issues in bulk
The Bulk issues import feature allows non-administrative users to import issues to Jira. External system import, which is described above, is available only for Jira Administrators.
With Bulk issues import, you should also import issues from a CSV file. But the entry point and steps to run Bulk issues import differ from External system import.
The Bulk issues import functionality has the following restrictions:
Prepare the CSV file with your Jira issues as described here. To import the file:
Map the fields in the CSV file to the issue fields in the selected project. If you want to map a specific field value in the CSV file to a specific Jira field value, select the Map field value checkbox.
Select the Next button.
If you selected the Map field value checkbox for some fields, you should map the values of these fields from the CSV file to the specific values of corresponding Jira issue fields. For example, you may want to map the CSV field value βFeature Requestβ to the Jira issue typeβs field value βNew Featureβ.
If needed, save the configuration for further use. For example, you may want to use the same field or value mappings for the next imports.
Select Begin Import when youβre sure of the configuration.
Administering Jira applications Support
Products
Jira Software
Project and issue tracking
Jira Service Management
Service management and customer support
Jira Core
Manage any business project
Confluence
Bitbucket
Git code management
Resources
Documentation
Usage and admin help
Community
Answers, support, and inspiration
Suggestions and bugs
Feature suggestions and bug reports
Marketplace
Billing and licensing
Frequently asked questions
Viewport
Confluence
Versions
Importing data from CSV
Migrating from other issue trackers
On this page
In this section
Related content
Still need help?
The Atlassian Community is here for you.
The Jira Importers plugin, which is bundled with Jira, allows you to import your data from a comma-separated value (CSV) file. This might be helpful when you are migrating from an external issue tracker to Jira.
CSV files are text files representing tabulated data and are supported by most applications that handle tabulated data (for e.g. Microsoft Excel, databases, etc.).
The CSV import feature allows you to import issues from an external (issue tracking) system which can export its data in a structured/tabulated format (preferably CSV).
The CSV import process consists of:
On this page:
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 any content that must be treated literally, such as commas and new lines/’carriage returns’ themselves are enclosed in quotes.
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 column
The CSV file import wizard (below) uses a CSV file’s header row to determine how to map data from the CSV file’s 2nd row and beyond to fields in Jira.
The header row should avoid containing any punctuation (apart from the commas separating each column) or the importer may not work correctly.
The header row must contain a column for ‘Summary’ data.
Commas (as column/field separators) cannot be omitted
For example, this is valid:
. but this is not valid:
Encapsulating Jira data 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 example, upon import, Jira will treat the following as a valid CSV file with a single record:
Treating special characters literally
Use double-quote marks ( » ) around a section of text to treat any special characters in that section literally. Once this data is imported into Jira, these special characters will be stored as part of Jira’s field data. Examples of special characters include carriage returns/enter characters (as shown in the example above), commas, etc.
To treat a double quote mark literally, you can ‘escape’ them with another double quote mark character. Hence, the CSV value:
Aggregating multiple values into single Jira fields
You can import multiple values into a Jira field that accepts multiple values (e.g. Fix (for) Version, Affects Version, Component, Labels). To do this, your CSV file must specify the same column name for each value you wish to aggregate into the mapped Jira field. The number of column names specified must match the maximum number of values to be aggregated into the mapped field. For example:
In the above example, the Component field of the second issue and the Fix Version field of the third issue will generate multiple values in appropriate Jira fields upon import.
Importing attachments
You can attach files to issues created from your CSV file. To do this, specify the URL of your attachment in an ‘Attachments’ column within your CSV file.
Creating sub-tasks
You can create sub-tasks of issues through a CSV file import, by encapsulating this structure in your CSV file. To do this:
In the example above, the fourth issue will be sub-task of the second issue upon import, assuming you match the ‘Issue ID’ and ‘Parent ID’ fields in your CSV file to the Issue Id and Parent Id Jira fields, respectively during the CSV file import wizard.
Importing issues into multiple Jira projects
You can import issues from your CSV file into different Jira projects through a CSV file import. To do this:
How to handle unresolved issues
For fields mapping to Resolution, Priority, and Issue Type, you will get a select list with the available values in Jira. In addition, you can quickly create values that do not exist in Jira by clicking the green plus symbols.
For fields mapping to Status, you will get the select list with Jira’s available values, but no plus symbol for creating new status values.
For these four fields, there are two special options in the select list in addition to Jira’s available values:
Importing worklog entries
Your CSV file can contain worklog entries. For example:
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:
This will populate the Multi Select Custom Field with multiple values.
Importing cascading choice custom fields
You can import values to a cascading choice custom field using the following syntax:
The ‘->’ separator allows you to import the hierarchy.
Updating existing issues
From version 4.3 of Jira Importers plugin you can update existing issues. Your CSV file needs to contain a column that during the import wizard is mapped to Issue Key. If an issue exists for a given key it will be updated. For example:
First row will create an issue, second row will set votes to 7, and add two labels. Following row will change the summary. Issue TT-2 will be created with two labels, the second row will remove those labels with a special marker >.
Running the CSV file import wizard
Before you begin, please back up your Jira data.
On the Setup project mappings page, you can either import all your issues into either one Jira project (new or existing), or multiple Jira projects (by ensuring that your CSV file includes the minimum Jira project data required β i.e. the Jira project name and key). Complete the following fields/options:
Choose either of the following:
Click the Next button to proceed to the Setup field mappings step of the CSV file import wizard.
At least one of these fields must contain data for Jira’s Summary field.
The Summary field must be specified for one of your Jira fields and the Next button will remain unavailable until you do so.
For CSV fields which have been aggregated by the CSV file import wizard, you will only be able to select Jira Fields that support multiple values.
Leave a field cleared or clear any content within it if you wish to import the value ‘as is’.
Congratulations, you have successfully imported your CSV data into Jira! If you have any questions or encounter any problems, please contact Atlassian support.
Tips for importing CSV data into Jira fields
Below are some helpful tips when importing data from your CSV file into specific Jira fields:
CSV data is imported on a per-project basis. You can either specify an existing Jira project(s) as the target, or the importer will automatically create a new project(s) for you at time of import.
This is the only required field.
You can import issues with multiple components by entering each component in a separate column.
You can import issues with multiple ‘Affects Versions’ by entering each version in a separate column.
You can import issues with multiple ‘Fix Versions’ by entering each version in a separate column.
You can import issues with multiple comments by entering each comment in a separate column.
Please use the date format specified on the second step of the CSV import wizard.
Please use the date format specified on the second step of the CSV import wizard.
Please use the date format specified on the second step of the CSV import wizard.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Issue Type as specified in your Jira system Defining issue type field values. You can also create new Jira values on-the-fly during the import process.
Import issues with multiple labels by:
If not specified in your CSV file, imported issues will be given the default (i.e. first) Priority as specified in your Jira system Defining priority field values. You can also create new Jira values on-the-fly during the import process.
If not specified in your CSV file, imported issues will be given the default (i.e. first) Resolution as specified in your Jira system Defining resolution field values. You can also create new Jira values on-the-fly during the import process.
Can only be mapped to existing workflow statuses in Jira. If not specified in your CSV file, imported issues will be given the default (i.e. first) Status as specified in your Jira system.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
The value of this field needs to be specified as number of seconds.
You can choose to have the importer automatically create Jira users for any values of the Assignee or Reporter field.
If you wish to import any other fields, you can choose to map them to specific Jira custom field(s). If your custom fields don’t yet exist in Jira, the importer can automatically create them for you. If your custom field is a date field, please use the date format specified on the second step of the CSV import wizard.
ΠΡΡΠΎΡΠ½ΠΈΠΊΠΈ ΠΈΠ½ΡΠΎΡΠΌΠ°ΡΠΈΠΈ:
- http://support.atlassian.com/jira-software-cloud/docs/create-issues-using-the-csv-importer/
- http://support.atlassian.com/jira-cloud-administration/docs/import-issues/
- http://confluence.atlassian.com/adminjiraserver/importing-data-from-csv-938847533.html
- http://confluence.atlassian.com/adminjiraserver085/importing-data-from-csv-981155358.html