At our organisation we run a large number of automated cucumber tests in Jenkins and use the existing
automations/cucumber/ api to upload the results to our Data Centre instance of Zephyr Scale. Unfortunately, this does not update the relevant Jira issue so it is not possible to see the status of the test executions that are relevant to the Jira issue inline. This coupled with the automatic generation of a test cycle name as Automated Build mean that we have no way to identify a test cycle as evidence that a story is tested and ready for release.
Previously we were using the cloud version of Zephyr scale and this functionality was present so we were able to do the automated linking, in moving to the datacentre version we have lost a capability we previously relied on.
|As a...||Test Lead|
|I would like...||To be able to add a Jira issue link to an existing test cycle (created by the cucumber automation rest api)|
|So that I...||Can automatically update a Jira issue with the results of automated test execution run in an external CI server (Jenkins)|