Sync Zephyr releases with Jira releases or sprints
As a test lead/manager, I'd like Zephyr to automatically create new releases and sync Stories by watching Jira for new releases (or sprints) so that, when I create a new release (or sprint) in Jira, a new release is created in Zephyr and the Stories magically show up. OLD ID:- ZENT-I-39
JIRA-Zephyr BDD testcase naming consistent with ZE Vortex automation.
Probelm Statement : There is test case name inconsistency between JIRA BDD plugin and ZE Vortex automation. In case if a scenario has 2 Examples table rows, then JIRA BDD plugin will create 2 test cases with identical test names, e.g. "scenario" and "scenario". While in case if test cases are being created through Vortex for the same type of scenario, they will have different names, e.g. "scenario" and "scenario 2". For Cucumber 7 which we are using right now in our framework, here is the naming conventions: “Scenario - Example #1.1”, “Scenario - Example #1.2”, etc. Previous version of JIRA BDD Plugin, it was creating test cases for all Examples table rows with the SAME name, which was inconstant with how Cucumber default JUnit report was doing, which was giving some indexing to each test case name. Due to this , when we are executing BDD testcase created (containing exdample tables) from JIRA using zephyr, results being attched to same testcase . Current and expected testcase naming snapshots are attched Reference :Case #00535844: Test Case name inconsistencies between JIRA BDD Plugin and Vortex automation
Jira Integration - Link an existing Jira ticket to failed test cases
Currently in ReadyAPI 3.0, it is allowed to create a new Jira ticket but it is not possible to link to a test case. It would be helpful to attach a JIra ticket/tickets to a failed test case. Jira ticket could be of any type(bug, enhancement, task etc.) Clicking on that linked JIra ticket, it will open in Atlassian. Regards, NeenaNeed a utility for Jira to remove inactive links to Zephyr test cases
We need a utility for Jira (could be a script to execute manually, periodically), which can go through Test Links and remove those that are incorrect/inactive – e.g. Test is deleted in Zephyr but the link is still there. This may happen when there are intermittent connection issues. Having incorrect/inactive links in Jira may cause audit issues. The utility can be executed with a parameter Jira JQL query that returns requirements to be cleaned up. OLD ID:-ZENT-I-370