When importing a feature file multiple times, if the test key tag is not present, the test is always updated regardless of the Scenario Text given.

Description

When importing a feature file multiple times, if the test key tag is not present, the test is always updated regardless of the Scenario Text given. 

Currently, when importing a feature file, the rules are as follow:

1. If Test key is present in the file:
    a) exists in Jira, the system tries to find the Test by key and update it; else...
    b) does not exist in Jira, the system returns an error message.
2. If the Test key is not present in the file, the system tries to find the Test having:
    a) same summary; else...
    b) the same summary in the target project; else...
3. Create Test in that project. The tags used in the scenario/scenario outline are also added as labels.

However, this is not happening when importing the same file with different Test Scenario /Scenario Outline and without any Test Key tag.

Instead of creating new Test Issues as expected, the same test imported the first time is being updated.

Pre-conditions

• Have some Feature files to import without Test Issue Key tags:
  • Sample: Sample_FeatureFile_NoKey.feature

How to reproduce

• Import the feature file a first time.

• • This should create a new Test within the Target Project.
• Import the same feature file a second time.
  • This should update the same Test created in the previous step, as the Scenario / Scenario Outline is the same.
• Change the Scenario / Scenario Outline for the test in the feature file and import the file one more time.

Actual result/Attachments

The import process is always updating the same test created the first time the feature file was imported. This happens regardless of any change within the feature file, including the changes to the Scenario / Scenario Outline.

See Attached Gif.

Expected result

If no Test Issue Key tag is present and the Scenario / Scenario Outline does not match any Summary in the target project, a new Test should be created.

Workaround

• If the file name is changed, then New Tests are being created correctly.

• • However, on a second import, the same problem happens.