Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,459,645
Community Members
 
Community Events
176
Community Groups

Traceability, by Feature, how can I see the whole structure? Feature > Stories > Test Cases>Defects

Edited

Zephyr for Jira: Traceability TAB - If I select "Feature" in the "Type" then I generate "Requirements to defect", I get the list of all the test cases associated to that feature but not the stories under that feature that are linked to those test cases. In that way, I don't know which story has been tested and which one has not. 

I would like a report by Feature > Stories > Test Cases/Story > Defects.

Instead of: feature > test cases > defects.

I know I can do  report by story, but by feature it would provide an higher level of visibility, where I can see the stories covered by test cases and the ones, under the same feature, with no test cases associated to it yet. 

Thanks

1 answer

0 votes
Steven Colón Marketplace Partner Oct 23, 2020

Hello @lsullivan

Thank you for the question.

At the moment, Zephyr for Jira is only able to create a traceability report from Requirement > Tests> Executions > Defects (and vice-versa) where "Requirement" can either be a Jira Story or Feature. So you'd have to do multiple reports and correlate them together manually at this point (maybe via CSV export).

I like your idea for a more "multi-tier" traceability report that can incorporate more data and I assume others would too. 

If possible, it'd be great if you could share your idea in our Zephyr for Jira Cloud Ideas Portal. Our product team will be happy to learn more about this feature and other users can vote on them as well. 

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events