As system, whenever importing Cucumber feature files, issue keys should be parsed from the tags

As system, whenever importing Cucumber feature files, issue keys should be parsed from the Cucumber tags, allowing the identification of:

• Tests
• Pre-Conditions

If the Test or Pre-Condition is identified from the issue key, then it is used to uniquely identify the issue, so no new issue is created is that one exists. (the previous rule of identifying tests by the summary should have less priority)

If the label refers to test sets or test executions, then it is basicaly ignored.

Note: the idea is that if we try to export and then import feature files using the REST API, it should be idempotent. Take into account the prefixes configured in Xray used for generating cucumber feature files.

Note: pre-conditions should also be found primarly by key and, if not available, by summary