Test Case - Import and Export

 -

TestRay import only supports Jira system field (e.g. Summary, Priority ...) and custom fields from Jira standard field types (e.g. Checkboxes, Date Picker ...)

Jira advanced field types (e.g. Development Summary, Global Rank ...) and any field types from third party apps are not supported.

Summary

This is the only required field.

Issue Key

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

Due Date

• Use the syntax that complies with the Java SimpleDateFormat

• Example: set date format to yyyy-MM-dd h:mm a if you are going to import date time value as 2030-01-01 12:00 AM

Labels

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

Epic Link

Provide Epic issue key if you want to link issues to an existing Epic in Jira.

Custom field types:

• Date Picker

• Date Time Picker

• Use the syntax that complies with the Java SimpleDateFormat

• Example: set date format to yyyy-MM-dd h:mm a if you are going to import date time value as 2030-01-01 12:00 AM

Custom field types:

• Checkboxes

• Labels

• Select List (multiple choices)

• You can import issues with multiple values by entering each value in a separate column.

• Values for 'Checkboxes' and 'Select List (multiple choices)' fields require to be pre-defined in your Jira server.

• Values for 'Labels' field are not required to be pre-defined in your Jira server, values will be created by import process.

Example:

^{Summary, Checkbox, Checkbox, Checkbox, Label, Label "First issue", value1, , , Label1, "Second issue", value2, , , Label1, Label2 "Third issue", value1, value2, value3, Label1,}

Custom field types:

• Number Field

• Text Field (multi-line)

• Text Field (single line)

• URL Field

• Values for those fields are not required to be pre-defined in your Jira server.

• Values will be created by import process.

Custom field type:

• Select List (cascading)

• The '->' separator allows you to import the hierarchy.

• Values for this field require to be pre-defined in your Jira server.

Example:

^{Summary, Cascading Custom Field Example Summary, Parent Value -> Child Value}

Custom field type:

• User Picker (single user)

• It requires to specify Jira 'username' in csv file in order to make a successful import.

• The user(username) specified in csv five must be defined in Jira server already.