While pulling Traceability Report, why are all executions listed when the search is for a version, In the image below the 3 executionslisted are from 3 different versions and all are listed when searched for one Version and Story.
This looks some what out of place.
Thanks for your interest in Zephyr.
Please note that the Versions that the dropdown values take into account is the of "Fix Version" and not "Affects Version".Chances are all the test executions that you are getting listed is having the same Fix version?
I think I was not clear enough in the first post,
Given that : -
- The Test Cycle is associated to a Version,
- Story is associated to a version [from your response Fix Version]
Assumption: Test Case's association to a version should not matter
Now to pull traceability , I select a version and a Story;
From the listed stories I select one and generate traceability from [Requirements --> Tests --> Executions --> Defects]
In the result, Test Cycles from Versions other than the one selected are also displayed.
The scenario is that the Test Case(s) attached to the story are regression cases and were executed in the past for a diffferent story; but pulling a report now should bring up only Test Cycles for selected version.
Please lete me know if this explains the issue.
Thanks for the explanatation
We would recommend you to raise a ticket with our support team so that one of our engineers can contact you and proceed accordingly on this issue as generally all the test executions only in aprticular version should be displayed in Traceability report
Can you sign up to our support site "https://support.getzephyr.com/hc/en-us" and use the option "Submit a Case" to raise ticket with us and one of our engineers would immediately contact you on this?
Did this issue get fixed as i am having the same issue with the report. I have all tests that i want to report on with the fix version applied. However when i generate the report it shows the tests that have been tested in previous version, the previous tests do not have the fix version they have the affected version applied but are still being pulled through. Any ideas on how i can fix this. It makes the tractability quite confusing.
Project managers know this problem: A “mountain of work” lays in front of you, and you don’t know how and where to tackle them. Different to-dos lie ahead, but just one task after the other can be ha...
Connect with like-minded Atlassian users at free events near you!Find an event
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.Host an event
You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events