(9.4-en) Import requirements

You are allowed to import requirements from a CSV file, requirement hierarchy and test case associations can also be imported.

Points to remember while importing Test Cases:

1. Summary or Issue Type is mandatory to start Import
2. Appropriate date format is required when processing with date fields
3. 'Issue Id' and 'Parent Id' fields are mapped to maintain requirement hierarchy information:
   1) 'Issue Id' & 'Parent Id' column could be either 'blank' or with any 'texts'
   2) Once 'Issue Id' and 'Parent Id' are exactly same, the Parent<->Child relationship will be established after importing
   3) If 'Parent Id' equals to an existing requirement issue key (Jira Issue Key), the imported requirement issue will be linked as a child requirement for the specified issue
4. Map Test Case ID (Jira Issue Key) in Test Case column if you want associate test cases to imported requirements
   Note: if Test Case ID specified in import file cannot be found in your Jira project, the Requirement will still be imported without Test Case associations
5. Providing ISSUE KEY will update the corresponding issue, if found
   
6. Specify Requirement Suite path in the Requirement Suite column if you want to import Requirements to the existing Requirement Suite
   Note: If the Requirement Suite path specified in import file cannot be found from your project, the Requirements still can be imported without Requirement Suite

To import requirements from .csv file, follow these steps:

1. Click "Import" button
2. Select requirement CSV file
3. Specify a "Delimiter" if necessary
4.  Click "Next" button
5. Map the fields in CSV file to corresponding Jira fields
6. Click "Import" button

[Screenshot - UG93_Requirement_Import_1]

You can find requirement import sample file here: Requirement_Import_Sample_File_v9.3.csv