Not able to bulk create stories following online help

[Yung Chen]

I am using a self-hosted version of JIRA. 

In following the instructions to create issues using CSV import, I am not able to move beyond step 2: Click more ( ••• ) > Import issues from CSV.

When I click on Issues > Search for issues on step 1, I see the following screen but am can't find the more ( ••• ) > Import issues from CSV on the screen

[somethingblue · Accepted solution]

Hi Yung,

Take a look at the Server's instructions for Creating issues using the CSV importer.  The steps are as follows:

Running the CSV file import wizard

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

1. Select Issues > Import Issues from CSV to open the Bulk Create Setup page. (If you do not have the option Import issues from CSV, your JIRA Admin must update the JIRA Importers plugin to version 6.2.3 or above.)
2. On the Setup page, select your CSV Source File.
   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 installation.
   
   • 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 ask you if you want create a configuration file that you can use for subsequent CSV imports.
3. Click the Next button to proceed to the Settings step of the CSV file import wizard. Complete the required fields.
   • If your CSV file uses a different separator character other than a comma, specify that character in the CSV Delimiter field. If the separator is a 'Tab', this can be entered using the format '/t'.

4. Click the Next button to proceed to the Map fields step of the CSV file import wizard. Here, you can 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, tick the checkbox for Map field value.
    Note: You must map a CSV field to the issue's summary field. This ensures the issues created have a summary.

5. Click the Next button to proceed to the Map values step of the CSV file import wizard. On this step of the import wizard, you can select which specific CSV field values you want to map to which specific issue field value. For example, your issue types you may have a CSV field value of "Feature Request", which you may want to map to the issue type field value "New Feature".
    Please note:

   • Any fields whose Map field value checkboxes were selected in the previous step of the CSV file import wizard will be presented on this page.

   • Leave a field cleared or clear any content within it if you wish to import the value 'as is'.

   • If you are importing a username-based CSV field (e.g. Reporter or Assignee) and you do not 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 have not already been defined in JIRA. 

6. 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.
7. If you're confident your import is correctly set up, click the Begin Import button. Your import will begin and once complete you will be informed of any errors. If you'd like to check your import first, click the Validate button and JIRA will validate your import and inform you of any expected errors or warnings. You can then go back and correct these before running your full import.

Please review the above linked knowledge base for further information.

Cheers,

Branden