...
- Issue Key: Unique identification of the entity e.g. “Issue Key” in JIRA. This is the base on which all the entities are identified uniquely.
- Issue Type: The type of entity e.g. “Story”, “Bug”, “New Feature” are “Issue Type” in JIRA.
- Summary: A short description of the entity e.g. “Summary” of issues entered in JIRA.
- Description: More detail information regarding the entity e.g. “Description” of issues entered in JIRA.
- Priority: The precedency of the entity like “High”, “Low”, etc.
- Versions: A number or tag denoting a particular edition of the entity.
- Components: Sub-sections of the main product/project.
- Labels: To identify a particular category of the entity.
- Test Data: Test Data is provided to execute the Test Steps with.
- Expected Result: Expected Result is mentioned against the provided Test Data for Test Steps.
- Platform: The environment the test will run against.
- Automation Id 1: It is mentioned for test scenarios and Test Cases that are imported for automation testing.
- Automation Id 2: It is mentioned for test scenarios and Test Cases that are imported for automation testing.
- SubLevel: It indicates association of a test case with test scenario. The column is marked with " * " mark unlike a test case under Story.
- Attachment: The Attachment column in the excel sheet which contains path on wards the excel file location on the drive. The issues that lie on the mentioned path are get attached to Jira as Issue Attachment.
- Folder Path: Test Cases will be imported in the path mentioned in the Excel file. If the folder does not present in Jira, then the folder will be created as per the path in the file.
- Custom Fields: Custom fields created in Excel as per requirement.
Note : QMetry import utility does not support third party add-on fields. To import third party add-on fields users can use Jira's import after QMetry issues are imported through QMetry import utility.
List of Supported Fields in QMetry Test Management for JIRA
...