Documentation for JIRA 6.3 EAP developer (EAP) releases only. Not using this? See below:
(JIRA 6.2.x documentation | JIRA OnDemand documentation | earlier versions of JIRA)

Skip to end of metadata
Go to start of metadata

The JIRA Importers plugin, which is bundled with JIRA, allows you to import your data from a comma-separated value (CSV) file. 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:

  • JIRA does not provide a dedicated import tool for and
  • Can export its data in a structured/tabulated format (preferably CSV).

(info) 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:

  1. Preparing your CSV file (below).
  2. Running the CSV file import wizard (below).
    • You can choose to map individual fields and field values during the import process.
    • At the end of the CSV file import wizard, you will be given the option of creating a CSV configuration file, which contains the settings you configured whilst running through the CSV file import wizard. This is useful if you need to test your CSV file import on a test JIRA server first before performing the import on a production system.

(warning) Please Note:

  • 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 one of these other methods than to first export your data from that system to a CSV file and then import that CSV file into JIRA. If your other issue tracking system is listed on the Migrating from Other Issue Trackers page, try using the appropriate method for that issue tracker (which is accessible from that page) to import data into JIRA.
  • If you want to raise a bug report or improvement suggestion about this feature, please do so within the JIRA Importers plugin project.

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.

(info) 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 (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:

  • "Clicking the ""Add"" button results in a page not found error"
    once imported, will be stored in JIRA as:
  • Clicking the "Add" button results in a page not found error

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.

(warning) 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 which 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 within your CSV file.

(info) 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:

  • Your CSV file requires two additional columns whose headings should be named similarly to Issue Id and Parent Id.
  • Ensure each regular (non sub-task) issue is given a unique (sequential) number in the Issue Id column. Do not include any value in the Parent Id fields for regular issues.
  • To create a sub-task of a regular issue in your CSV file, reference the unique Issue Id number of the regular issue in the Parent Id column. Do not include any value in the Issue Id fields for sub-tasks.

For example:

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:

  • Your CSV file requires two additional columns whose headings should be named similarly to Project Name and Project Key.
  • Ensure that every issue represented in your CSV file contains the appropriate name and key in these columns for the JIRA projects to which they will be imported.
    (info) The project name and key data is the minimum JIRA project data required for importing issues from a CSV file into specific JIRA projects.

In the example above, the first and second issues will be imported into the 'Sample' project (with project key 'SAMP') and the third issue will be imported into the 'Example' project (with project key 'EXAM') , assuming you match the 'Project Name' and 'Project Key' fields in your CSV file to the Project name and Project key JIRA fields, respectively during the CSV file import wizard.

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:

  • 'Import as blank' — this causes the JIRA value to be blank for that field. Note that, if you are importing Unresolved issues, you should create a field mapping for the Resolution field and set the value 'Unresolved' to 'Import as blank'.
  • 'No mapping' — this attempts to import the value in the CSV file as-is. Note that using 'No mapping' for a field value will result in a failed import if the value is not valid for that JIRA field. For fields mapping to Status and Issue Type, default values are used when the 'Import as blank' option is selected.

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.

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 <<!clear!>>.

(warning) 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: If your JIRA installation has existing data — Back up your existing JIRA data.

  1. Log in to JIRA as a user with the JIRA Administrators global permission.
  2. Select Administration > System > Import & Export > External System Import > Import button associated with the Comma-separated values (CSV) option to open the CSV File import page.
    (tick) Keyboard shortcut: g + g + start typing external system import
  3. On the CSV File import page, select your CSV Source File. If you want to change the file's encoding and CSV delimiter format, click the Advanced heading to reveal this option (as shown in the above screenshot).
    (info)  Note:
    • The file will be imported using the File encoding you specify here (which is UTF-8 by default).
    • If your CSV file uses a different separator character other than a comma, specify that character in the CSV Delimiter field.
  4. Leave the Use an existing configuration file check box 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.
    (info)  Note:
    • If you select this option, you will be asked to specify an Existing Configuration File.
    • If you do not select this option, then at the end of the CSV file import wizard, JIRA will create a configuration file which you can use for subsequent CSV imports (at this step of the CSV file import wizard).
  5. Click the Next button to proceed to the Setup project mappings step of the CSV file import wizard.
  6. 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:

    Import to JIRA Project

    Choose either of the following:

    • Select a project and then do either of the following:
      • Start typing the name (or key) of a project that already exists in JIRA or use the dropdown menu to select an existing JIRA project.
      • Select Create New from the dropdown menu and in the resulting Add A New Project dialog box, type the following:
        1. A new project Name
        2. A new project Key
          (info) This will be used as the prefix for all issue IDs in your JIRA project.
        3. The Project Lead.
    • Defined in CSV. Ensure that every issue in your CSV file includes data for the JIRA Project Name and Project Key.
      (tick) This option is useful if you want to import issues from your CSV file into multiple JIRA projects. See Importing issues into multiple JIRA projects for details.
    E-mail Suffix for New UsersEnter the email address domain for any new users specified in the CSV file which will be added to JIRA during the import.
    Date format in import fileSpecify the date format used in your CSV file. Use the syntax that complies with the Java SimpleDateFormat.
  7. Click the Next button to proceed to the Setup field mappings step of the CSV file import wizard.

  8. On the Setup field mappings page, specify each CSV Field (determined by your CSV file's header row) you want to import into your chosen JIRA project by selecting their check boxes under the Import column on the left.
    (info)  Please Note:

    • At least one of these fields must contain data for JIRA's Summary field.

    • If your CSV file contains more than one of the same field name specified in its header row, the CSV file import wizard will aggregate these into a single field, which will be marked by a (warning) symbol at this step of the wizard.

  9. In the JIRA field column, select the JIRA fields you want to match to fields defined in your CSV file (i.e. each CSV Field you selected in the previous step). For more information about matching CSV fields to JIRA fields, see Tips for importing CSV data into JIRA fields below.
    (info)  Please Note:

    • 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.

    • If you are importing sub-tasks, remember to match the Issue ID and Parent ID fields in JIRA to those in your CSV file.
    • If you are importing issues into multiple projects, ensure that you selected Defined in CSV during the Setup project mappings step above and remember to match the Project Name and Project Key fields in JIRA to those in your CSV file.
  10. To modify the values of any fields' data in the CSV file before they are imported into JIRA, select the Map field value check boxes next to the appropriate fields.
  11. Click the Next button to proceed to proceed to the Setup value mappings step of the CSV file import wizard.
  12. On the Setup value mappings page, specify the JIRA field values for each CSV file field value (which has been detected by the CSV file import wizard).
    (info) Please Note:
    • Any fields whose Map field value check boxes 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 '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 clicking the Add new ... link (e.g. Add new issue type 'subtask' shown in the screenshot above) next to the appropriate field.

    • If you are importing a username-based CSV field (e.g. Reporter or Assignee) and you do not select the Map field value check box 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.
      (info) Regardless of whether or not you select the Map field value check box, JIRA will automatically create usernames based on the data in your CSV file if they have not already been defined in JIRA. 

  13. Click 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.
    (info) Note:
    • If you experience problems with the import (or you are curious), click the download a detailed log link to reveal detailed information about the CSV file import process.
    • If you need to import another CSV file with the same (or similar) settings to what you used through this procedure, click the save the configuration link to download a CSV configuration file, which you can use at the first step of the CSV file import wizard.

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:

JIRA Field

Import Notes

Project

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.

Summary

This is the only required field.

Issue KeyYou can set the issue key for an imported issue. If an issue with a given key already exists in JIRA, it will be updated instead.

Component(s)

You can import issues with multiple components by entering each component in a separate column.

Affects Version(s)

You can import issues with multiple 'Affects Versions' by entering each version in a separate column.

Fix Version(s)

You can import issues with multiple 'Fix Versions' by entering each version in a separate column.

Comment Body

You can import issues with multiple comments by entering each comment in a separate column.

Date Created

Please use the date format specified on the second step of the CSV import wizard.

Date Modified

Please use the date format specified on the second step of the CSV import wizard.

Due Date

Please use the date format specified on the second step of the CSV import wizard.

Issue Type

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.

Labels

You can import issues with multiple labels by entering each label in a separate column.

Priority

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.

Resolution

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.

Also see How to handle unresolved issues for helpful tips.

Status

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.

Original Estimate

The value of this field needs to be specified as number of seconds.

Remaining Estimate

The value of this field needs to be specified as number of seconds.

Time Spent

The value of this field needs to be 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 as active accounts in JIRA. Users will need to get their passwords emailed to them the first time they log into JIRA.
  • Users with no real name will get the portion of their email address (login name) before the "@" character as their Full Name in JIRA.
  • If you are using External User Management, the import process will not be able to create JIRA users; instead, the importer will give you a list of any new users that need to be created. You 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 will be stopped. A page will be displayed showing a list of users that can't be created.
  • If Assignee and Reporter are not mapped, then no usernames are created

Other fields

If your 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.

195 Comments

  1. Anonymous

    Apparently no Jira event are fired during the creation of issues. Is this feature planned for the next release ?

    1. Hi,

      This feature request is tracked here. Your comment and vote will help us prioritize it.

      Cheers,
      Wojtek

  2. Anonymous

    While attempting an import, I got the following error:See attached example illustrating field labels to change.]id,10169 (SQL Exception while executing the following:INSERT INTO customfieldvalue (ID, ISSUE, CUSTOMFIELD, PARENTKEY, STRINGVALUE, NUMBERVALUE, TEXTVALUE, DATEVALUE, VALUETYPE) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?)
    (Data truncation: Data too long for column 'STRINGVALUE' at row 1))

    I have two questions:
    Is it possible to control the length of a text custom field or do I have to
    pre-process the data before importing so it does not exceed the field's length?

    What is the field length of a text custom field?

    Thanks.

    1. Hi,

      Do you use JIRA Importers plugin or the old built-in CSV importer?
      The importer is designed to truncate text field for summary only.
      For other fields IIRC we don't truncate the text and in this case you need to pre-process your CSV file before importing it into JIRA.
      I've raised an issue for that - JIM-235

      Text Field custom field must be shorter than 255 characters.
      Alternatively you may use a Free Text Field which has no restrictions on its length.

  3. Anonymous

    First I thought that i can import the selected data from csv to the current existing issues but it seems that it doesn't

    happen  that way. Instead of that its creating new issues. I have a following objective , is this process helful in that ?

    - I have a CSV file with two fields issue number and type (text field)

    - In my jira i have these feilds i.e the issue number and type (custom text field)

    I need a way which will help me to place "type" i.e text field from CSV to the existing JIRA issue " type" field.

    - is this possible ? on the basis of common jira issue key can i import the custom field to the existing issue

    If not through the import process is there any other way ?

    1. The importer does not support such scenario.
      Feel free to raise an improvement request for it.

      You can achieve it now with Jelly script or by using remote API (SOAP or XML RPC).
      In both cases some coding will be necessary.

      Cheers,
      Wojtek

  4. Anonymous

    I am trying to import from a CSV file into Jira using the instructions above, but the "CSV Import" capability displayed above has a different wizard than what I see when I  try to execute my import.

    I see the following two fields instead of the 4 fields and "Start Import Wizard" displayed above:

    1. * CSV Import File

     - with the following subtext "Enter a filename to import data from. Files will be loaded from: /home/jira/jira/jira-home/import/csv" 

    2. Existing Configuration File

     - with the following subtext "Enter a filename of your configuration file. No configuration file? Run the Import Wizard first. Files will be loaded from: /home/jira/jira/jira-home/import/csv"

    I am in version 4.2 but the documentation related to 4.2 still points me here.

    Any recommendations would be appreciated.

    1. Hi,
      This documentation (and screenshots) refers to the importing capabilities provided by JIRA Importers Plugin which is bundled with JIRA 4.2.2 or newer.

      For JIRA 4.2 you can just install JIRA Importers Plugin and then you will see the new way of importing from CSV.

      Cheers,
      Wojtek

  5. Anonymous

    Hello,

    I am using the "External System Import - Beta!" from Jira "4.2.4-b591" to import data in csv format (saved in excel file). I have two columns that I want to map to "fixed versions". One is the major and the other is minor version. But once imported only two values from those versions are created in Jira and assigned to the issues properly, the rest are empty. Not sure why?

    Also I have a column that is just plain text notes and I want to map it to comments, so I chose map to the comment body, but all comments are empty. I appreciate if anyone can help with this problem.

    1. Hi,

      The first part looks like a bug which has been fixed recently in 1.7.5

      WRT the comments - it looks like we have a more serious bug that we thought. We are tracking it here and I've just bumped up it's priority.

      Cheers,
      Wojtek

      1. WRT the problem with importing comments -> I posted more details about how it works.
        If you have still problems with importing comments - comment on this issue or raise a new bug there.

  6. Anonymous

    How can I import into cascading list? I have values in to CSV fields, and in Jira I created this as a cascading list. What is the best way to map it to a cascading list?

  7. It seems that importing comments using the PvcsComment mapper is broken, is this intentional? Is there a current method for importing comment authors and times?

  8. It appears the Jira imports issues via .csv in random order. Is there any way to preserve the ordering of the imported rows? 

    1. That was a regression already fixed in 2.3.1.

      1. So apparently it is back?  Note that I'm using 4.3. Also, I'm specifically not talking about comments being out of order, but the issues themselves. The ordering of the issues imported does not match the ordering in the csv.

        1. Oh I see. BTW: I am taking about JIRA Importers Plugin (JIM) version 2.3.1 which is released independently from JIRA. Make sure to update your JIRA Importers Plugin to the most recent version. JIRA 4.3 OOB does not come with the most fresh version of JIM.

          1. Yes, I updated to the latest and greatest and had the same result.

            1. Thanks for reporting it, that's a bug. I raised issue https://studio.atlassian.com/browse/JIM-369 to track it. Going to fix it now and we'll attach a fixed version there.

  9. Anonymous

    Hi, is there any way to import an issue and put directly it on the watchlist of a usergroup / several users?

    1. At the moment no. Feel free to raise such request and we will consider adding support for it.

  10. Anonymous

    Hi,

    I have a requirement to create the report the Issue in an excel sheet and login to JIRA and create a new ticket in JIRA . We need to create the above steps using Excel VBA code.

  11. Anonymous

    The new importer doesn't seem to handle carriage return characters in CSV cell values. I managed to import the same CSV file using the old importer without any problem.

    Also it would be nice to be able to reference existing JIRA issues when importing sub-tasks (e.g. by setting the value of subtask-parent-id to an existing JIRA iissue ID).

    1. Thanks for letting us know. Would be great to get a sample from you for tests because I don't follow you there - you mean line breaks are not understood or the carriage return character is not stripped from the text?

      Raised https://studio.atlassian.com/browse/JIM-421 for the sub-tasks idea.

      1. Anonymous

        The import fails altogether. I've raised JIM-426 and attached example files

        1. Looks like I'm seeing a related to similar issue. I have created .csv and .txt (tab delimited) files with Excel and they don't import into Jira. The issue may be related to the multiline text fields I'm trying to import. The annoying thing is that Excel doesn't accept its own .csv file either. Do you still need data files to reproduce/debug this? We are using 4.3.2 and the dialogs look identical to the ones shown above.

          Thanks,

             Sander

      2. Anonymous

        I have a similar problem... when I import a CSV, the line feeds within the description field vanish... I had formatted text (means - with line feeds) in my CSV, after importing one sentence is after another, the formerly clear text is hardly readable, e.g. Java error messages and such.

        It seems the linefeeds are just filtered out by the importer (to avoid the above mentioned exceptions?) and I cannot find a way to get those linefeeds into JIRA - <br /> or <br> or <p> are not interpreted by JIRA and just appear like that (plain text) on the screen. \n vanishes.

        Any ideas? Or is this really a bug? Why does nobody else have this problem since may???

        Thank you in advance! (smile)

        1. To all of you having problems with line feeds in CSV - we for couple of versions used a different CSV parser, but now we're back to the old one that proved to work best. So if you're experiencing problems please do upgrade to the newest version. It will work as it used to with the old importer. We had some legal issues with the old parser that's the reason for temporarily switching to another but since they were sorted out we could go back.

          1. Anonymous

            I have Importer Plugin 3.5.3 with JIRA 4.4 - guess, that's updated. The line feeds vanish. (sad)

            1. Not sure what could be wrong here. Please raise a support issue and attach a sample file then we'll be able to investigate. What operating system do you use?

              1. Anonymous

                I would raise a bug - but although I am admin for JIRA, I do not have the support account mail information... (sad)

                JIRA is running on Linux, the webpages are displayed on Windows with Firefox or IE. A sample file would just be pretty short, just insert some \n in the description field... Could you raise a bug report for me, please?

                1. Anonymous

                  ah, Database is MySQL

                2. Inserting \n doesn't reproduce it. I just tried myself a long multi-line text and it worked fine for me. Remember you need to put " before and after the text.

  12. I was just looking at the examples you attached to https://studio.atlassian.com/browse/JIM-71. I can't see any way to set the comment's author and creation date when you import in the CSV.  That would obviously be a non-starter, since we are importing comments made in the past by various users, so would need that data.  Am I missing something?

    1. I already see that you found out about PvcsComment mapper.

      If anyone's interested I'll put a sample at https://studio.atlassian.com/browse/JIM-464

  13. Anonymous

    Hi

    I installed the plug-in from the below site :

    https://plugins.atlassian.com/plugin/details/32645

    But after installation, whats the next step? Its not clearly mentioned anywhere. Kindly help.

    Thanks

    Mehala

    1. Anonymous

      Sorry there was a typo in my previous message. I downloaded the jar file of importer plug-in. What is the next step after download? How do i make it appear in the administrator page? Please help

      Thanks

      Mehala

  14. Hello,

    We use a custom workflow. However, when importing from CSV, JIRA does not request a Workflow to associate the issues with. In the CSV, when I set the Status to 'To be Approved' (my custom initial status after Issue creation) the application returns the following error:

    This seems to be happening because JIRA assigns the 'jira' workflow to the created project, which does not include the specific status. The problem is that, even when I map the status to 'Open" during importing, and after assigning my workflow to the project (after importing), I can not set the status to the desired value.

    So, my question is: How can I define the workflow to be used before (or during) the CSV is imported? Otherwise I guess I would have to make the "status" and "assignee" parameters editable through the issue screen which is not desirable...

    Thank you,

    Michail

    1. Hi Michail,
      you can't at least in CSV. We introduced this feature to other importers but CSV is behind (hopefully in the future will fix it).

      Status is not something you edit. It's a result of a transition you make. So everything you need is already in JIRA - you need to use Bulk change -> Transition issues.

      So, import issues to a project, change the workflow and use Bulk change is issue navigator to modify all of them at once.

      Cheers,
      Pawel

    2. To get around this problem in Jira 4.1.1, I created the project manually beforehand with the custom workflow assigned to the project.  I then choose the option to "import into an existing project" and then select the newly-created project.  I haven't yet tried this in Jira 4.4, but I am getting ready to shortly.  One catch, you need to make sure the default workflow is active - in order to do this, I just create a dummy project that uses the default workflow.

      1. That sounds like a good workaround of this limitation. AFAIK in modern version of JIRA Importers Plugin we don't need anymore the default workflow to be active.

      2. Thank you for the replies. I have managed to find a workaround by simply creating a project and then assigning the desired workflow to it before CSV importing. After this, importing a CSV file to the specific Project will apply the issues on the customized workflow.

  15. When importing comments from CSV, I put before them the following pattern : "15/08/2011 09:31; dirtech ;" . As long as the comment contain only one line, all work fine: the comment is marqued reported by dirtech on August, 15th, . But if my comment contains 2 or more lines, I got a warning : "commenter null not allowed, using currently logged user".

    This is not very critical, as the comment is imported, but annoying: I got a lot of these warnings, and it is difficult for me to see real warnings :-(

    Any clue ?

    1. Please upgrade the plugin to the newest version. We fixed this problem recently.

  16. Anonymous

    failed to import a custom checkbox list from csv file

    4 columns VS 1 custom field
    I am trying to import 3 columns to the 1 custom field

    please tell me how to import to a custom field called Impact in business that i already created

    when mapping using csv there was no problem, it was successfuly imported but I can only see one value or (one marked)

    but in some case i have in CSV 3 columns that have value instead of NULL means i should have in the custom field 3 checkboxes marked and not only 1 marked

    If i need to fix the CSV geneated from sql please correct me
    because the old database they are saving the properties of checkbox in 4 columns in the same table

    ImpactInBusinessVelocity ImpactInBusinessVelocity ImpactInBusinessVelocity Velocity Revenue Generating NULL

    if you think you do have another way please share it with me

  17. Hi,

    does anybody know whether it's possible to schedule CSV files import?

  18. Hello,

    I am successfully importing a CSV file into JIRA 4.3 but it seems that no new Custom Fields are created. JIRA accepts the configuration but I can see no Custom Fields in the resulting Issue Screens.

    Example line of Configuration File:

    Any idea on what may be wrong?

    Michael

    1. Did you configure custom field to show up on the default screen? If not it will not be visible.

      Also you can check the log to see if custom fields were created.

      If still unsure raise a support request at https://support.atlassian.com and attach your files there.

  19. Anonymous

    Hi

    I have a big migration task which we renewed the version of JIRA and screen design at the same time.

    All mappings are working correctly and import is successful..but I have problem with imported issues list on Activity stream. All imported issue numbers are crossed with a line. Which it seems like you deleted and it cannot be reached. but issue is there in the database.

    Actually I don't care how it looks to users in the Activitiy Stream but when  I try to clone those issues clone is not working on them.

    I need urgent answer.

    Thanks

    Serhan

    1. Please raise an issue at https://support.atlassian.com - I'm not sure why you are not able to Clone, do you have any errors in the log (file atlassian-jira.log)? Or is it just that Clone operation is not in issue ops bar (could be a result of using non-default permission or workflow scheme)?

      It's hard to tell if it's JIM fault or some issue with JIRA. Please upgrade JIM to the newest version and then try importing again (clear previous issues first) - I remember one bug which caused issues to NPE when accessing history which potentially could influence Clone too.

  20. Hi,

    what is the correct syntax to attach files via the CSV-Importer? I've discoverd that it's possible to attach a file via a URL.
    Is there also a way to add attachments via a local directoy on the server?

    The Attachment is imported with the credentials of the Administrator. Is it possible to modify the "username" and / or "upload date"?

    In Jira 4.4.1 the options of page-6 are not shown, so it's not possible to change these options!

    • Create new versions' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new versions for imported versions which do not already exist in JIRA.
    • 'Create new components' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create new components for imported components which do not already exist in JIRA.
    • 'Create new custom fields' — It is generally recommended that you leave this set to 'ON'. Only select 'OFF' if you do not want JIRA to automatically create custom fields for imported fields which do not have a corresponding field in JIRA.
    • 'Maximum issues and failues' — If you wish, specify a maximum number of failed issues after which the importer will stop. If you want the import to continue regardless of any failures, leave this field blank. If your old issue-tracker has a large number of issues, it's generally a good idea to run first the importer on a limited number of issues (e.g. 100), then manually inspect the imported issues to confirm whether your configuration file was specified correctly. When the results are satisfactory, you can run the import with no limit.

    With 4.3.2 these options are visible.

    Thanks

    Udo

    1. It's not possible to set the owner. Attachments are always imported with the current user. Raise a feature request at https://studio.atlassian.com/browse/JIM

      Options you mentioned were removed some time ago.

  21. Hi,

    when uploading an attachment an automatically comment like

    "Attachment EL_an_Schumann_Betreff%2333160%20Liste%20Gesasav2%20Version%2012.02.txt has been added with description: https://xxx.xxx.xx/migration/33160/EL_an_Schumann_Betreff%2333160%20Liste%20Gesasav2%20Version%2012.02.txt"

    will be generated. Is there an option to disable these comments.

    Thanks,

    Udo

     

    1. No, there's no option for that.

      1. Hi Pawel,

        is it possible to get the source code, so that we can make our own changes here?

        Thanks,
        Udo

        1. Hey,

          The source code is available in the source distribution of JIRA (available for any commercial license holder). As we usually release new versions of JIM more often than JIRA, you may need to wait for the sources of the most recent version.

          Cheers,
          Wojtek 

  22. Anonymous

    How does the import process works if there are issues with the same issue-code? I don´t want duplicates. 

     

    1. JIRA doesn't allow issues with duplicate keys so no worries.

    2. JIRA Importers Plugin does not decide which issue keys will be used - that's something JIRA auto-generates for every created issue. So there can't be duplicates (as long as JIRA behaves correctly).

  23. The old version of the CSV import allowed you to create the configuration file WITHOUT having to actually start the import. This is expecially useful if you want to generate the majority of the config file, but need to make some tweaks before you actually run the import.  Why was this functionality removed?

    1. That change happened for the sake of simplicity. Most of our recent design decisions were driven by this factor.

      However adding a link (or a button) on the final page to download the configuration file would be probably a reasonable thing.

      Feel free to raise an issue at https://studio.atlassian.com/browse/JIM - especially if more people vote on it, we will reconsider adding such capability.

      Meanwhile just start the import and immediately cancel it. Then you will get the link to the configuration file you can reuse.

  24. Anonymous

    I´m importing issues but i can´t import the date fields like creation date.

    I recieve this log: 

    2011-10-30 17:59:28,843 WARN - Unable to parse created date: [23/09/2010]
    2011-10-30 17:59:28,843 WARN - Unable to parse due date: [23/09/2010]
    2011-10-30 17:59:28,843 WARN - Unable to parse created date: [13/07/2010]
    2011-10-30 17:59:28,843 WARN - Unable to parse due date: [23/07/2010]
    2011-10-30 17:59:28,843 WARN - Unable to parse created date: [23/09/2010]

     

    this is my look and feel date configuration:

    Date/Time Formats

    These time and date formats are used throughout JIRA. To specify them, use the format described at http://java.sun.com/j2se/1.4.2/docs/api/java/text/SimpleDateFormat.html.

     FormatExample
    Time Formath:mm a6:03 PM
    Day FormatEEEE h:mm adomingo 6:03 PM
    Complete Date/Time Formatdd/MMM/yy h:mm a30/oct/11 6:03 PM
    Day/Month/Year Formatdd/MM/yyyy30/10/2011
    Use ISO8601 standard in Date PickerOFF

     

     

     

    1. Well, recent version of JIRA Importers Plugin allow you to configure the date format during the import process. So maybe you're using some old version or the old importer (the one that was built into JIRA <= 4.2)? Please try to use the newest version, you'll be able to specify the date format.

  25. Hello,

    I am currently experiencing a (small) problem on CSV importing and I need to get it resolved asap as I will be depending on it for the next months.

    Everything works fine; my problem is that any kind of information corresponding to Custom Fields does not appear on the issue screen. All data seem to be correctly mapped and accepted by the importer, field mapping works fine. Actually, only one Custom Field works fine and gets rendered properly (Text Field < 255). All other Custom Fields are gone after importing (including select boxes, txt fields, text areas etc).

    It could be related to Screens but if I manually add a new Issue in the same project where the CSV Issues were imported to, everything works fine and all Custom Fields are populated and rendered appropriately.

    Can someone help me on what may be going wrong?

    For your convenience I am attaching the CSV configuration file:

    Thank you.

    ./Michael

    1. This site is a bad place to ask for help. We are polluting more and more the original documentation.

      Could you please raise a support request at https://support.atlassian.com providing also an excerpt (a few lines of your CSV files should be enough) of your CSV file and details like which JIRA version you use and which version of JIRA Importers Plugin. We may ask you also for XML dump of your JIRA instance. That please is secure and you could share there some sensitive data.

      My first sight at your config lights up a red light at line:

      "field.Asset" : "customfield_Systm(s) Affected:com.atlassian.jira.plugin.system.customfieldtypes:textfield"

      But it does not mean anything, without really testing it.

      Cheers,

      Wojtek

  26. I do not see the Story Points field listed in the Jira Fields on Setup Fields Mapping screen.

    I've added Story Points to Default Screen because I read in one of the comments only fields in the Default Screen are available. I also made this field globally available.

    I understand this is a custom field created by GreenHopper so would expect that it appears either as a custom field or issue field.

     

     

    1. What version of JIM and JIRA do you use? Currently GH creates Story Points field that is Number custom field type. In this case when you change context to global you should see it - it will be in custom fields section.

       

      1. It's on a test server running Jira 5.0.2 and GreenHopper 5.9.4

        On the production server (Jira 4.4) Story Points are offered in the mapping.

        Consider it a peculiarity of the test server setup. Thanks for the feedback.

        1. That sounds strange. Could you please raise a support request for it and pass us your JIRA and GH configuration (DB XML dump - feel free to sanitize/anonymise it) and your Importer cfg file (unless you did not use it) so that we can try to reproduce it.

          1. I've worked around the issue. Can I ask if Import yet supports importing sub-tasks to existing issues?

            Example where I already know the Parent IDs and want to import a number of sub-tasks for each issue.

            We tend to define Stories in advance and some are on the backlog without sub-tasks. When sub-tasks are defined they are either imported as sub-tasks of nothing (when import throws an error because I've omitted a row defining the parent), or it creates a new parent (parent row included in csv) with the sub-tasks.

            Jira also lacks ability to bulk re-parent issues, from what I've attempted.

  27. Anonymous

    Is it possible to import Issue Links through the CVS importer ?

      1. Is there any plans to provide this capability?  I am currently trying to use JIRA to manage my organisations standard service delivery lifecycle (key deliverables etc).  Combining this import capability with one of the Gantt Chart Plugins would have been very very sweet.  I wanted to define the standard deliverables (with dependencies) as issues in a spreadsheet and then import that spreadsheet with minimal manipulation for each new delivery project that came along.  Any thoughts ?

        Cheers,  Rich...

        PS: Please improve the CAPTUA, takes me several attempts to get one through.

        1. Please raise an issue for that at https://studio.atlassian.com/browse/JIM

  28. Hi,

    I have other ways to import Issue Links?

    1. You can use Jelly tags to link issues after import - Jelly Tags#jiraLinkIssue

  29. Anonymous

    Hello

    I'm uploading sub tasks using CSVs and link them to issues. However i would like to update the External Issue ID at time of upload so once they are in JIRA i can perform queries for reporting.

    Apparently i can import Labels but not the External Issue ID, however once imported i can query on External Issue Id and not Labels.

    Can somebody tell me wheter there is a way to upload External Issue ID from CSVs or query on Labels ?

    Thanks in advance.

    Regards.

    fred.

  30. I am not sure if I follow you here.

    If you import data into JIRA Label field, then you should be normally able to run queries against it. External Issue ID is actually just an internally used custom field which allows us to detected whether given issue has been already imported or not. It's used in other importers (like Bugzilla or Mantis). It does not bring much sense wrt CSV importer and personally the presence of it here I treat as a bug rather than a feature.

    Because it's extremely difficult to have such conversation when someone posts questions as an anonymous user, I strongly recommend using https://answers.atlassian.com/

    Cheers,

    Wojtek

  31. Anonymous

    Hi Wojtek

    Thanks for replying. When i'm saying i cannot query i mean that i cannot query on labels using the ~ in the JQL. Basically i want to be able to see all issues still open for labels starting with IT-WD for example ... i can do this with the External Issue ID but not on labels ...

    Is it clear now ?

    Regards.

    fred.

    1. Got it now. Yes, you are right labels support just the exact search. We use normal text field (< 255 chars) for External Issue ID and that's why it supports querying with ~. But that's an accidental thing rather than a bug.

      Have you considered importing this data (IT-WD*) into a separate custom field which would support free text search?

      Cheers,
      Wojtek 

  32. Hi,

    I can to add multi comments to existing Issue by CSV importer? If no, how I can do it?

    Ann

  33. Actually you can do it in JIM 4.2+. You need to put an existing issue key on each line followed by comments (each comment in a separate column), you can also place each comment on a separate line with an issue key attached.

    Later during wizard you'll be able to map columns to Comment and Issue Key respectively.

  34. Pawel, thank you for reply, but

    I`m sorry, I don`t understand. I have Jira 4.4.  I import projects from old server to new. I`m using CSV importer. I only began this work, so feel some problems.

    I alredy import some Issue without comments. But now I have to add multiple comments to each of them.

     I don`t know what is JIM 4.2+ ((

    On 3rd step "Fields" I can to add Coment body or Issue KEY, but I can`t to link them.

    Help me please, and give me more detailed explanation!

    Ann

     

    1. Short answer is that you will not be able to add comments to existing issues using JIRA Importers Plugin (also known as JIM) in JIRA 4.4. JIRA Importers Plugin version 4.2 and above gives you this feature but they require JIRA at least 5.0.

      You wrote that you had already imported some issues but without comments, what stopped you from importing comments the same time you were importing issues? That's supported and you can do it easily, just for each issue you have in CSV add comments in the same line.

      1. Thank you! I understanded that I can`t add comments to existing issues in my version Jira.

        You wrote "what stopped you from importing comments the same time you were importing issues?". Try to explain: a standart export to Excel in my version Jira not allow to export comments. So I did a "select" and wanted to add it to existing issues 

        1. Oh, I understand, you were migrating from JIRA to JIRA. In this case you may consider using a backup from the old one and restoring it to the new one.

  35. Ok. thank you. I`ll try to do like you said

  36. Where it says:

    Updating existing issues

    From version 4.3 you can update existing issues.

    It should really say:

    Updating existing issues

    From JIRA Importers (JIM) plugin version 4.3 you can update existing issues.

    I just wasted time to prepare a CSV update file and had to find that Issue Key does not exist even though I am using JIRA version > 4.3 (4.4.5).

     

    Yes I know, I should not check the latest documentation when using an earlier version (wink)

    1. Hey, I've fixed that. You are right, that could be misleading even for the users who use the newest version of JIRA, but without the newest version of JIRA Importers Plugin. 

      Thanks,
      Wojtek 

  37. Anonymous

    In the CSV I would like to add a column with an exiting issue id to which I want to link the issue being imported.

    For instance, I want to link the issue being imported to the existing issue DOC-1234. So I would like to add a column "Link to" with the value DOC-1234.

    Is that possible today?

    Thanks

    Joerg

     

    1. No, issue links are not supported for CSV yet.

  38. Anonymous

    Hi All,

    Apologies in advance because I think I must be missing something obvious here as a JIRA newbie. My issue is that I can't seem to link the Issue Id and Parent ID during a CSV import in order to import subtasks. I don't see Parent ID or Issue ID in the pull down menu on the Issue Field Mapping page. I tried saving my importer-configuration file and adding the lines:

    field.Issue ID = Issue ID

    field.Parent ID = Parent ID

    but that didn't work. When I mislabeled the fields IssueID and ParentID (no space) I saw an error at the bottom of the Issue Field Mapping page, however with what I wrote above I see no error, even though my Issue ID and Parent ID field still show up with a mapping of "None".

    The only other thing I can think of is that I am importing these subtasks as a custom subtask I created called a Milestone. So I tried setting their types to just regular subtask and that didn't work either.

    I am currently out of ideas. Any thoughts? Thanks in advance and sorry for posting anonymously–trying to limit proliferation of accounts!

    -Sarah

    1. Please contact support to resolve this issue. Attach your sample CSV file and configuration.

       

  39. Anonymous

    I have a similar problem with importing subtasks.

    I use the sample csv file text from above which I cut and pasted into my file and map the fields accordingly and I get the following error. I am using the latest version of the importer as well ( 4.3.2.).

     

    Issue 'TF-205' is not of a sub-task type (subtask). It will NOT be a sub-task of the issue 'TF-8'

    1. Well, the value for issue type "subtask" is invalid in your JIRA. It's unfortunate mistake here, JIRA by default comes with "Sub-task" issue type. I'm going to change the example here to match the defaults. Please change your file and it should work.

       

  40. Hi,

    I am trying the existing importer plugin available, saved the issues in excel file, saved as .csv file and tried to import the same using project information contained in the csv file option.

    "project key TESTMP-1330: You must specify a unique project key, at least 2 characters long, containing only uppercase letters"

    my csv file contains all of them as unique value.

    why is the error coming?

    1. Project key should be TESTMP here. TESTMP-1330 represents Issue Key in JIRA.

  41. When I try to import a csv file to my project, I get the message "no matches" in the "Import to JIRA Project" field on the Set up project mappings site. Yet, I have a project.

    What could be the problem?

    Thanks in advance

    1. Hi, if you are an OnDemand customer I think you are facing recent regression - https://studio.atlassian.com/browse/JIM-815 and  JRA-29659 - JIRA Importers Plugin (JIM) won't show the projects list when you import CSV file Resolved . We are working on it at the moment.

      1. Thank you, it is fixed now and i can move on.

  42. Anonymous

    Ive got the same question as the other anonymous regarding cascading lists; how can one fill a cascading dropdown?

    1. It's not currently possible. We don't support this custom field type.

  43. Seem to not be able to connect csv heading names to project field names on the "3. Setup Fields screen" 

    1. Not all of the JIRA Project fields are available to choose from. 
    2. Both custom and standard fields display the problem
    3. Example
      1. Epic/Theme, Story Points are fields in JIRA but do not show up in Setup Fields dropdown
      2. Network is a custom field that is in JIRA but not in the dropdown.

                
    4. "You are using version 4.3.2. For help with this plugin please contact JIRA support."
    1. Please update to the newest version. Custom fields visibility on the mapping page was recently improved.

  44. Anonymous

     I want to update comments to an existing issue already imported. How can I map the issue key. I do not seem to find issue key as part of mapping the fields from CSV to Jira

  45. Use Issue Id field on the mapping page.

  46. Hi! I am trying to import a csv file to Jira. I got it that the summary column is mandatory in the csv file, but what are the values that have to be typed into the column??? It is possible that I did not understand well what kind of data can be imported. I am trying to import a list of names for a drop-down list. I have the impression that the other users only import issues?

    Thanks for any hint

    1. Yes Eva, importer is meant to import issues only.

      But it has this great feature of creating some missing details in JIRA (like Resolutions, Issue Types or custom field values). So you can hack it to do what you want - you can make an issue in CSV that will have some values for the select custom field. When it's imported they will be added to the custom field. So in the result you will fill the custom field with values you want. If you need help with it go to https://support.atlassian.com and raise a support request.

      1. <Wow> That was a fast answer! I will raise a support request because I want to create an issue type with fields showing the list of names and phone numbers and I want the users to edit it and a few more things.

      2. Anonymous

        Pawel,

        Can you elaborate on the "hack"?  For example, if I have two custom fields (Customer, Customer Phone Number) I can create a CSV that includes three columns of data that represents those custom fields + a placeholder summary field.  And then I would have to go back into JIRA (after running the import) and somehow delete those issues because they are essentially placeholders for the customer field data? 

        1. Here's an example, imagine you have an empty select custom field (with no options defined), then you can add new options using following file:

          During the import wizard you will map Custom Field Option column to the select custom field.

          When you import this file Option A, Option B and Option C will be added to the select custom field. If the field is multiselect it's even easier and you can place all values in one line:

          Then you delete imported issues as they are not needed and you're done.

          Is it clear for you?

  47. Anonymous

    Does any specific configuration need to be done to make the Issue Key available (for mapping) when importing data from a csv file?  I am currently unable to see this field in order to do bulk updates from an external data source.

    1. Please upgrade to the newest version. This option is not available in older versions.

  48. When you put examples into the documentation they should either work or you should remove them because broken examples just confuse people and waste their time. You claim that we can use Joda Period Formatting for Worklogs and provide the following example:

    Summary,Worklog
    Only time spent (one hour),PT1H
    With a date and an author,2012-02-10 12:30:10;wseliga;120
    With an additional comment,Testing took me 3 days;2012-02-10 12:30:10;wseliga;P3D

    However if you try to import this you get the following error:

    Import completed with 2 warnings:

      • Exception occurred parsing worklog 'PT1H'. It will be skipped
      • Exception occurred parsing worklog 'Testing took me 3 days;2012-02-10 12:30:10;wseliga;P3D'. It will be skipped

    Why is this broken?  When importing tasks it is very common to import a time estimate for that task but it currently seems the only way to import a value for this is in seconds. Who estimates tasks in seconds?!!! Fail.

    1. I'm really sorry for your wasted time, the documentation was incorrect and currently you may use only seconds. Already fixed the documentation. I understand it would be great to use Periods and I raised an issue for that https://studio.atlassian.com/browse/JIM-861

  49. Hi,

    When I click on the External System Import tab, I get the following error.

    Not Found (404)

    Cannot autowire object because the Spring context is unavailable. Ensure your OSGi bundle contains the 'Spring-Context' header.

     

    I am using JIM 5.0.2 and JIRA 5.1.6.

    Scott Deschenes

    1. Please raise an issue at http://studio.atlassian.com/browse/JIM and attach your atlassian-jira.log, and then we'll check what's going on.

  50. Anonymous

    Is there a mechanism for importing non-English data?  I've used the CSV import tool successfully multiple times.  However, when I try to import Chinese characters, I use Excel's Unicode text file and JIRA doesn't seem to dig that too much.  Specifically, JIRA tells me something like this:

    Failed to read CSV file, you may decide to ignore the error: java.io.IOException: Malformed CSV stream. Missing [,] near offset 7 after field 0 on line 42

    1. Did you set the encoding on the first page of the import wizard (in Advanced section)? This could be a reason.

      Please try asking this question on http://answers.atlassian.com or contact our support at http://support.atlassian.com

  51. Hello,

    I'm using JIRA 4.4.5 with JIRA import v3.5.3 the lastest available version for 4.4.5. I would like to update existing issue in my JIRA database by import a CSV file. I try a lot of different things but I couldn't find how to link, from my CSV, the Issue ID to the Issue ID of JIRA, like in the exemple. In the Column JIRA field I do not have "Issue ID" Could you help me please.

    Thx

    1. That's not possible. JIRA Importers Plugin 3.x doesn't have this feature. You need to upgrade.

      1. Thx for you answer. Is it possible with another plugin ?

        1. You could try using JIRA Command Line for that.

  52. I am trying to import issues from a CSV file with (5000 issues). I am using runfromCSV to import the issues but i am disabling the notification scheme and making sure the default assignee is Unassigned but i am getting errors. Please help me to solve the following issues .

    1. def runJenkinsStep1 = "cmd /c //myJiraInstance/JenkinsHome/userContent/Atlassian/jiraTestAdmin.bat --action updateProject --project $projectKey --notificationScheme \"Disabled Notification Scheme\" --defaultAssignee unassigned " 

      def runJenkinsStep2 = "cmd /c //myJiraInstance/JenkinsHome/userContent/Atlassian/jiraTest.bat --action runFromCsv --file $sourceFile --propertyFile $propertyLocation --common \"--project $projectKey\" --continue "

      def runJenkinsStep3 = "cmd /c //myJiraInstance/JenkinsHome/userContent/Atlassian/jiraTestAdmin.bat --action updateProject --project $projectKey --notificationScheme \"Default Notification Scheme\" --defaultAssignee unassigned "



       Error i am getting is : Process Error: Error: Unknown flag 'defaultAssignee'. Error: Unexpected argument: unassigned

    2. My CSV file has lot of special characters like ? " " / ' ( ) - . ,

      Error i am getting is :  Remote error: com.atlassian.jira.rpc.exception.RemoteValidationException: {summary=The summary is invalid because it contains newline characters.} : []

     

    1. Ad. 1) Please contact the tool creator for support. I don't know what jiraTestAdmin.bat is, and how it works.

      Ad. 2) Please make you encode special characters correctly (and you clean your data), there's a section above about quoting characters and preparing your CSV file.

       

  53. Following the instructions above for importing worklog items from a CSV file (at Importingworklogentries), I can successfully import worklogs but the time is never cumulative. The time on the worklog entry always overwrites any time entry previously created. How do I import worklog items that accumulate time so that I can see total time spent as the sum of all worklog entries, rather than just the most recently entered time?

    1. I believe you want to map the column to Worklog (in seconds), not Time Spent (in seconds). The second one is allowed once per issue and replaces the previous value. Issue can have multiple Worklogs associated with it and they also have Time Spent part.

      1. I'm guessing that there's a way to accumulate time on a JIRA item, but I'm not getting it. So let me be more specific in my example. I started with the example CSV given above:

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

        And I adopted it to work as three updates to my own sample project as follows:

        Issue Key,Project Name,Project Key,Summary,Worklog
        TEST-34,Test project,TEST,,3600
        TEST-34,Test project,TEST,,20130210123010;mbrown;120
        TEST-34,Test project,TEST,,Testing took me 3 days;20130211123010;mbrown;259200

        The intent here is to have all three lines update a single JIRA item, TEST-34, in my project named "Test project". I had to adjust the date/time strings to match my desired format, but that was minor. Everything worked correctly except that the overall Time Spent on TEST-34 was 72 Hours, rather than 73 Hours 2 Minutes as expected. (3600 + 120 + 259200 should add to 73 hours 2 minutes, but instead the last entry of 295200 just forced the total time to 72 hours.)

        Here is the CSV mapping file I used. You'll note that the worklog column is mapped to field.worklog, not to Time Spent. Out of curiosity, how many fields can go into the Worklog column separated by semi-colons?

        {
        "field.Project Name" : "project.name",
        "date.import.format" : "yyyyMMddHHmmss",
        "field.Worklog" : "worklog",
        "field.Issue Key" : "issuekey",
        "field.Project Key" : "project.key",
        "user.email.suffix" : "@example.com",
        "mapfromcsv" : "true",
        "field.Summary" : "summary"
        }

         

        1. Please raise an issue for that at http://ecosystem.atlassian.net/browse/JIM

  54. Anonymous

    Hi, how can i do that JIRA not create new value in a customfield when i import csv file?

    1. By default new / non existing custom field values are created in JIRA. You can't disable that (you'd have to modify source code of the plugin which is by the way available through http://my.atlassian.com). All you can do is to map all custom fields values to those that exist, if you do that no new values will be created.

      1. Anonymous

        Can i do that JIRA tell me if he has created new value or can i tell her that creating new values is an error?

        1. No, you can't disable this feature. JIRA Importers Plugin unfortunately doesn't log values it create. It logs only new custom fields.

          Why do you need that?

          1. Anonymous

            i don't want to make 2 differents values like 'Min' and 'min' and sometimes more than 2. For another customfield there are a lot of values to map and i think some people who want to import can forgotten to mapping.

            1. I guess you're talking about Select and Multi Select, right? In their case Min and min are the same and JIRA Importers Plugin will not create duplicates.

              1. Anonymous

                i'm sorry you are right. so my problem is less serious now. thanks you for your help. I have one another question. beside that if i have 2 values like 'soft' and 'software', the only one solution i can have is to pay attention to my CSV file or to map my values?

                1. Yeah, the only way is to pay attention and map values. JIRA Importers Plugin source code is available so if you really need a feature like that you may consider changing the source code. You can also raise an issue for this feature at http://ecosystem.atlassian.net/browse/JIM

                  1. Anonymous

                    =) thanks you. when i was speaking with you about that i see that i can't map attachment. Have you any idea about what it is? (grant permision or other) the field not appear in JIRA customfield selection.

                    1. Are attachments enabled in your JIRA?

                      1. Anonymous

                        yes i think because i can do it when i create or change issues. my version of JIRA is 4.3.4. In the issue customfield selection in importer plugin, i have 19 customfield which is propose to me and the field attachment not appear.

                        1. Oh, you're using JIRA 4.3.4, JIRA Importers Plugin doesn't support attachments in this version. This feature was added in JIRA Importers Plugin for JIRA 5.x.

                          You can try using JIRA Command Line to migrate attachments. Or some other way.

                          1. Anonymous

                            Ok. Your help was really great. thanks you again. Have a nice day. =)

  55. Anonymous

    Hi, our company is using the web-based JIRA and we need to import many issues from our previous project manager. Does the JIRA Imports plug-in work for the web-based JIRA? Does the web-based JIRA already come with the JIRA Imports plug-in?

     

    Heres our JIRA information:

    Greenhopper (v6.1.3.2)

    JIRA (v5.2.6#..)

    1. You mean JIRA OnDemand, right? Yes, some of the importers are available in OnDemand. Please talk with support, they'll help you choose the best strategy for the migration. 

  56. Anonymous

    I'm in the process of importing a large project with over 500 issues.  There are at least 50 Epics related to a subset of these issues.

    Is there anyway to map an Epic to an issue or should I enter the Epics manually and then associate them?  If the answer is a custom field can you please explain how to use the custom field?

    1. Need to do it manually, importer doesn't support that.

  57. We are migrating a JIRA project from one instance to another, but only importing recent issues (key ids range from 2000 to 4000).  Since we also use Fisheye and integrate to SVN, the user requested that the JIRA key be retained in order to sustain the integration to SVN.  So, an issue with a key of XXX-2323, will now have a key of XXX-1 which will break the linking.

    Any thoughts?

     

     

     

     

     

    1. Anonymous

      If you using a recent version you can set an issue key when importing as it's described above.

  58. Anonymous

    When importing data from CSV what are the steps to follow in order to import the data. Means first import the seed data i.e projects,users,customers etc.

    And then import the issue headers > and then issue details such as comments, attachments etc.

    But where to find the database data structure OR sample csv template files for data migrating.

    Is there any step by step guide??

    1. Hey, from user perspective importing from CSV happens in 2 steps: you configure the import (using import wizard) and you run it (press famous "Begin Import" button).

      Before running the import you need to prepare your CSV file accordingly (typically it will be generated by some scripts on your side or exported from another tool). Basically every line (except for the headers) in CVS file maps to a single issue.

      Things like comments, attachments or worklogs all have to be put in the same line with other issue details like the summary. Because obviously there can be many comments, attachments or worklogs per issue, then you have to use a trick which is to create several columns (sometimes dozens of them - to fit all the comments from the mostly commented issue you are importing) for comments (and attachments and worklogs). If you name all these columns  in the same way, then in the import wizard you can easily map several columns at the same time to a single JIRA entity.

      All this is documented in "Aggregating multiple values into single JIRA fields" section in this page.

      And the examples used here should be also valuable to get the concept.

  59. Anonymous

    Thanks

    We have several thousand issues to be migrated to the new JIRA system.

    So is it possible to import history information for each issue from CSV import?

    Also is there any CSV template available with all possible fields of JIRA?

    1. Importing history is somewhat possible with the capability of updating issues - see Updating existing issues for more details. For each change (or set of related changes) you should have a separate row, but all of them mapped to the same issue key.

      However if importing history is really important for you, I would recommend using JSON importer which was built for this very purpose.

      WRT CSV templates - it's not possible to provide such template. You can have any number of custom fields in JIRA. Also the names of the columns in CSV really do not matter. Everything depends on how you wil map those columns (to which JIRA issue fields) in the importer wizard. Just try it out and I believe it will be clear.

      In case of further questions, please use https://answers.atlassian.com - the forum which serves for exactly such purpose.

  60. Anonymous

    Thanks for prompt response

    Is JSON importer available in 5.2? also I read it is beta version and not supported?

    What if that is not available is there any easy other option for importing history?

    1. JSON improter is available for JIRA 5.2. It's beta, because we haven't yet committed to the final shape of JSON files it supports.

      Beta does not mean here it's unsupported or bad. Think about Gmail which was beta for years (smile)

  61. Anonymous

    Hello,

    I would like to import data from another system using CSV format that uses its own reference for issue IDs and NOT use Jira's issue IDs, basically each row will have its reference/issue ID and want to use that in Jira. It doesnt seem possible or its unclear how to do it. thanks.

     

     

    1. Issues in JIRA need to handle some convention: alphanumeric part , hyphen, number (like ABC-123) where alphanumeric part matches the project key the issue belongs to. If issue IDs in the other system match this convention, then you can map such a column from CSV file to "Issue Key" and then JIRA Importers Plugin should preserve your issue keys (provided that you import them to the project with the matching key).

      If your issue ids don't follow JIRA convention, then you can import them to a custom field.

      1. Anonymous

        Thank you for the reply. Not sure if i explained the issue or understood your suggestions. Here's a snipplet of a fake CSV file:

        OldKeySummaryOwner
        HQ25319HelloX
        HQ26489HiY

         

        I'd like to use the values under column "Old Key" in JIRA and keep the values as they are, instead of JIRA starting to use a prefix from the project name and increment it. The JIRA issue key is used in "Projects", "Issues", "Agile board", ... I'd like to use the issue keys and their values as in the CSV file and have those values displayed anywhere in Jira. Basically preserving the link between the JIRA environment and our legacy tool and allowing users to work in both systems using the pre-defined issue keys from the old system. thanks for you help, regards!

        1. That won't work.

          Your issue keys have to follow the convention <Project Key>-<Issue number>.

          I recommend living with keys like HQ-25319 (provided that your project key is HQ, that will be possible) or alternatively import keys into a separate custom field - then you will have the old keys at hand.

  62. hi,
    I have a problem trying to migrate a CSV file in version 4.4.5 of JIRA.
    when you import the file does not load the specific data fields but if I make the issue. Checking file. Log tells me: Custom field 'Abogado Externor' is not available for all projects. Can not use it, going to create a new one.
     

    The prepared CSV file with columns and values needed.
     

    This migration of data into the 4.1.2 version did not have any problem
      

     Can you help me?

    1. A quick workaround for you would be to switch back to JIM 4.1.2 or to make a custom field global before the import, you can limit the scope afterwards.

      1. when i talk you about version 4.1.2, I'm mean to version the JIRA 4.1.2 and de create custom field global i have around the 40 or 50 fields. I've to make custom field global for each of my fields?

        1. Oh, it includes really old JIM. Sorry, I don't have any other workaround for you. The other approach for you would be to modify JIM's source code which is available for each JIRA licensee.

  63. Anonymous

    I would be really nice if one could define and use a secondary delimiter for multi-fields. For instance, when I import from Project (saved as csv), the Resource Name has commas in it.  So I have to break all of them out into additional Assignee columns. Would be so much easier if I could Replace(",","|") and have JIRA use the bar as a secondary delimiter.  The actual csv would go from


    Summary, Assignee, Assignee, Component, Component
    Task, Jonn, Jack, Infrastructure, Setup

     

    TO

    Summary, Assignee, Component
    Task, Jonn|Jack,Infrastructure|Setup

     

    Notice this would also get rid of jagged data.  I wouldn't have 5 Assignee columns with blanks in them just because 1 task just happened to have 5 assignees on it but none of the others did.

     

     

    1. JSON is a better format for structured data than CSV, so I'd try to use the JSON importer instead of hacking CSV.

  64. In section "Updating existing issues",  I suspect

    TT-2,,<<!clear!>>,<<!clear!>>,

    was meant to be

    TT-2,,,<<!clear!>>,<<!clear!>>

    -Johnny

  65. Anonymous

    Hello Team Altassian,

    We need to shift data from JIRA 5.0 to Cloud instance of JIRA 5.2. We have huge number stories with attachments like test cases, flow diagrams, etc with each story along with sub-tasks and stories linked with each one of them. How can we do the import-export without loosing the parent child relationship as well as retail the attachments. Please advice.

    Astha.

    1. You can import all your self-hosted JIRA data into JIRA OnDemand. It's described in detail at Importing Issues#ImportingissuesfromJIRA,JIRAHostedandotherthird-partyissuetrackers

  66. This should be available to project administrators for a given project.

  67. Hi,

    The CSV file import is possible for the Administrators only. Is there any way to allow non-admin users to import the csv comments.

    I have the source code of the jira-importers-plugin 4.1.4. Please help me regarding this.

     

    Regards,

    Patina

  68. Anonymous

    Hi,I am playing around with the updating existing issue and it does not seem to work well. First I have a plugin version 5.0.4 and JIRA version 5.2.11. On the test I first imported the csv with only one ticket (without the issue key field). JIRA assigns one to it after it's imported. I then manually added the issue key field on the same csv  file and modify the summary. On a 2nd attempt update I got the ticket skipped and from the log I read:

    2013-07-05 10:35:11,240 INFO - Importing: Issues
    2013-07-05 10:35:11,240 INFO - ------------------------------
    2013-07-05 10:35:11,240 INFO - Only new items will be imported
    2013-07-05 10:35:11,240 INFO - External issue 152529 already exists as TRYIN-1, not importing.

     

    Looks like it's set to only import new items. Is there a way to turn it in order it accept updates?

     

    Thanks for looking into the issue!!!

    1. The update functionality of the importer normally is used for updating regular JIRA issue (these ones which were not imported). During importing JIRA Importers Plugin puts an id (auto generated for CSV files) into a custom field (called External Issue Id) and then skips issues which have been already imported.with such id. 

      In your case the same random id could have been used. You can avoid skipping of such issues and enforce the update by removing External Issue Id custom field or clear it (with bulk edit) for all the issues you are interested in updating.

      Please ask any future questions at https://answers.atlassian.com

  69. The Updating existing issues section fails to mention that if you don't specify certain fields explicitly (e.g. Issue Type), they will be overwritten.

    A few more details here: https://ecosystem.atlassian.net/browse/JIM-827 

  70. Hello,

    I was wondering if anybody could point me to a solution here. The import works fine - however, characters such as "à", "é", "è" are not recognized after the import. I get little � everywhere.

    I exported the the CSV file using UTF-8 format and specified UTF-8 in the advanced options in the import wizard. Not sure what I am doing wrong.

    Cheers & best (smile)

    1. Following my comment here I raised a support ticket for my problem.

      In essence there is currently a Bug in the import process which does not take into account properly special characters. If this feature is important to you, please vote on it here:  JRA-35589 - CSV import does not handle French characters Resolved

      If you have problems importing your language properly, please comment on the Bug above so that your language can be taken into account with the fix.

      Cheers & best,

      Andreas

  71. Anonymous

    In case anyone comes to this page to do an import, an extra note for attachments - the JIRA importer doesn't cope with spaces in your file names, so make sure your attachment does not have spaces in the filename and therefore the attachment name in the Attachment column in the CSV, and any content links in the issue Description.

    1.  I think the attachment name neds to be encoded like a URL is

       

  72. If I set the issue key for every issue imported from a CSV file, does JIRA make sure that the next issue I create in the project will start at one higher than the last imported issue? Or do I need to reset the numeric part of the next issue key for each project myself?

  73. Anonymous

    Is it possible somehow to use other fields as Key while importing ? We're thinking about to build an interface from our ITSM System to Jira. We have specific identifier IDs in there, that aslo should be imported to jira. In my opnion it would be great if those ids could directly be used as reference.

     

    Otherwise we would need to export the JIRA Keys after importing the issus again, and bring them into the ITSM System, to get the reference, what, in my opinion, is not needed.

    1. Hello Anonymous,

      I am not sure if this is what you mean, but you can map your ITSM ticket number to the Issue ID - let's say your ITSM tickets are simple numbers (23456, 56342, etc.), you can create a project in JIRA (e.g. Key = ITSM) and then import your ITSM tickets via the CSV procedure.

      That would give you on the JIRA side an Issue ID: ITSM-23456 and ITSM-56342, etc..

      If you can configure in your ITSM system a calculated field, you can then create a link by using simply your JIRA URL + IssueID. For example: http://yourjiraserver.yourdomain.com:8080/browse/ITSM-23456

       

      Hope this helps!

      Cheers

  74. Is there a comprehensive list of field header names and which fields they map to in Jira?

    1. Hello Peter,

      you can place any header names in you csv file. During Import Wizard you will manually map headers to JIRA fields.

  75. Anonymous

    I am new to Jira, and was wondering where do we import our project requirements? Is it under Tasks?

     

    1. Could you be more specific with what you mean by "project requirements"?

      • Requirements for the entire project?
      • Requirements for each task/workpackage in the project?

      Cheers! 

  76. When I do my .CSV import the value of "Assignee" as well recieves the Developers role for the same project, howcome?

    Can't see that I map this anywhere.

    Thanks in dvance,

    M

    1. Hello Mathias,

      JIM is automatically adding imported assignees to the Developer role in Project - that's also the way all other importers are working (JSON, Bugzilla, Redmine, etc.)

  77. Anonymous

    Why is importing from Excel so hard?  Are your programmers just complete morons?  How hard is it to parse a date?  How hard is it to ask for confirmation after I import a bunch of items with errors instead of creating 190 bad issues?  

    In short, are your entire team complete amateurs?

    1. How hard is it to parse a date?

      Harder than one might think in my experience. How hard have you found it?

    2. We are really sorry that you are experiencing so many problems with our CSV Importer. We are aware that date handling may be unintuitive and importing unchecked data into project could be error prone and simply painful...

      We have an idea to create a "preview" step, which would validate all of the data before the actual import, but it's not yet planned for development.

      Thanks for sharing your frustration though - we could rethink our priorities and do it sooner.

      1. I would like to see a dry-run mode that would report all errors but not actually create issues that I later have to delete just because of one or two errors