Feature request: add path of mapped test cases to traceability export
In the export of Requirements traceability from ZETM, we would like an option added to export the path of the mapped Test case(s) for each requirement. Currently, a lot of test case info is included in the export but the Path (folder location) of the Test case(s) is not an option. OLD ID :- ZENT-I-459Enabling larger data set for number of requirements per traceability report
when user is running the traceability for requirements, the current limitation is 100 requirements per report the request from the user would be they would need more than 100 requirements per report and request is to enable larger data set so user can get more than 100 requirements per report . can you please help us in moving forward with this requirement OLD ID :- ZENT-I-344
Add ability to clone release
We have about 2500 tests at this time. As the process of connecting that many tests, even organized into test sets, is cumbersome (creating another suggestion for that issue), it would extremely helpful to be able to clone a release or iteration to another release or iteration, and carry across the linked items (we only use tests, not sprints or requirements). That way, even though I would have to manually link all the tests to a release, at least for the next release, I could clone and be done, and just add any new tests (or test sets).Automatic Traceability Links in Zephyr Scale Cloud
Hi everyone, right now, we are using Zephyr Scale Server in our company but we are (as a lot of users/companies probably are) evaluating the move to the cloud app. Now, regarding the traceability in the cloud app, I'm at a bit of a loss and maybe those, that already use the cloud app, can shed some light on this. Recently, we got a test account for the cloud app of Jira including Zephyr Scale and I have been looking into the differences between server and cloud. One thing that is very important to us as a financial service provider in Germany is the traceability between issues, test cases and test executions. I can link test cases to issues and link issues to test executions, just as I can do in the server app. In server, if you execute a test case covering an issue and you link another issue to the test execution, you automatically get the link between issue 1 and 2 (e.g. requirement and defect) shown in the respective issues. This does not seem to happen in cloud. All I get is the link to the impacted test execution. This means, that to trace the connection between requirement and defect I have to do a lot more work (clicks) than in server. For example, a defect is created from a test execution in Zephyr and assigned to a developer. He/she opens the issue and wants to know, which requirement is impacted by this defect. Since only the impacted test execution is shown in the defect, he/she has to click that, then click the corresponding test case and then go to the traceability tab of that test case to finally be able to get to the requirement. Also, I do not have the option to configure Zephyr in such a way, that test cases (including their execution history) are automatically linked to created defects (as 'blocked') which we use regularly to better manage re-tests of defects. So the question for all you cloud users out there. Am I missing something? Or is this really a limitation of the cloud app? Sorry for the long post and thanks in advance for any info. 😉 Cheers Josh
Missing Traceability on user screen
I have created a bunch of test cases, cycles and plans and have then created Confluence pages to document them through. When i save, i get the "Traceability" button at the top of my screen, my colleague does the same and he gets no traceability button. Is there a setting somewhere?
