I was wondering if it is possible to automatically copy (or link) defects listed within Test Details to the defects listed in the main Test Execution.
It would be helpful to be able to see either in a Test Cycle report or from the Plan Test Cycle screen to see any and all of the defects found within that particular test execution. As it stands right now, I need to link the defect to the actual test step, and then again to the main test execution.
It current is working as designed, and currently the bugs filed against steps don't roll up to the report locations. I'll send this feedback over to the development team and they can consider adding this feature in a future build.
On a related note, I take the report of step defects is still not available in 2.1 (as discussed in this conversation back in Apr : https://answers.atlassian.com/questions/153666/zephyr-attachments-to-jira-test-do-not-display-in-execution-of-test-cycle-issues-entered-in-step-do-not-display-in-test) ?
We have made many strides in terms of features and functionality in this area since this thread has begun. Currently there are three common scenarios that are often times confused as the same thing. I will detail these below and let you know which are current features and which are coming.
We thank you for your feedback and hope this clears up any confusion. If you have any questions or comments, please feel free to ask.
I am struggling with this as well. I am trialing Zephyr for JIRA v.22.214.171.1249. I failed an individual test step and created a defect from that step. I was expecting to see the defect ID show up on the Cycle Summary screen for that test, or even on the details screen for that specific test, but the only place I see the defect referenced is when I click the E button for that test again. I feel like either I am missing something re: how this is meant to work, or perhaps this is a bug??
I am also evaluating Zephir for Jira and found the same limitation, I consider that linking a bug to a test step is not advisable, one should always link to the test case not to lose the tracceability in the test cycle. However, we loose the granularity of the information, not knowing which step is affected.
Is this improvement on the Zephyr for Jira short term roadmap?
I am struggling with the same "problem". Chris wrote nov 2013 that is works as designed. Where can I find a description of the design so that I can understand the logic behind this. I "think" the same way as Mike and Gianni.
I'll take in consideration but I'm still looking for an answer for Zephyr.
Looks like v3.2.0 of Zephyr for JIRA add-on can create a link from the issue created at Test Step level(Test Details -> Defects) to the Test Case (https://answers.atlassian.com/questions/192640), but I still have a question: Does the field "Defects" from "Test Execution" section get updated automatically with the issues from Test Step level?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
Hello! I'm Rayen, a product manager at Atlassian. My team and I are working hard to improve the trial experience for Jira Software Cloud. We are interested in talking to 20 people planning t...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs