Page History
...
You can name the fields as you wish since they are going to be mapped during the importation process, but there are three mandatory fields that must be mapped:
- Test IDIssue Id – a unique identifier for the issue, this field is used to group lines that belong to the same test case or to identify a precondition or a test set.
- Summary – this field is mandatory since Jira doesn’t allow you to create an issue without a summary.
- Test Type – this field defines the test type of the each test to import. The test type must match one of the types of the project to which the test is being imported.
Here is an example of a source file as seen in a spreadsheet application:
Here is the same example as seen in a text editor:
| Info | ||
|---|---|---|
| ||
The issues can all be imported to the same project or into multiple projects, one column in the source file can be used to define the destination project (either by having its key or id). |
...
Besides these ones, if you have defined additional fields as mandatory for Test issues, then you will also need to specify their mapping.
Project field
The project to which the test will be imported can be defined for each issue in a field. The fields "Project Key" or "Project Id" can be used for this.
...