Description
When a cucumber file with a Background is imported via REST API, a Pre-Condition is created and associated with the cucumber Test.
Example:
@REPO-4 Feature: As a user, I can calculate the sum of 2 numbers Scenario: As a user, I can calculate the sum of two negative numbers Given I have entered -1 into the calculator And I have entered -3 into the calculator When I press add Then the result should be -4 on the screen
curl -H "Content-Type: multipart/form-data" -u admin:admin -F "file=@1.feature" 'http://localhost:8090/rest/raven/1.0/import/feature?projectKey=REPO'
This is registered on the Issue History of both the Test and the Pre-Condition:
- From the Test's perspective:
- From the Pre-Condition's perspective:
However, if you keep importing the same feature file for the same Test later on, repeated entries keep being added to the Issue History of both the Test and the Pre-Condition:
- Test:
- Pre-Condition:
Same imports should not be creating additional entries in Issue History
Given that enough imports are made, this could lead to thousands of repeated Issue History entries, and that would have an effect on Jira's performance.
Attachments
Issue Links
- relates to
-
XRAY-9836 As a system, Xray should comply with Jira's issue history guardrail
- New