It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Make requirement coverage depend on test fix version

As pointed out in this question, the requirement status is not calculated based on the test fix version. This creates problems when the requirement has a slightly different implementation in 2 different versions. When this happens the steps in the test for one version might have to be different than the steps in the test for another version. 

If we create 2 tests for the requirement, and we execute for one of the versions only, the requirement coverage will be listed as TODO and this is not desirable.

I'm requesting that an option is added to the administration page that the calculation of the requirement coverage is also dependent on the test's fix version.



Log in or Sign up to comment
Community showcase
Published in Marketplace Apps & Integrations

Cloud Cafe Ep. 1: Getting started with the Atlassian ecosystem

Welcome to Cloud Cafe – our video series about cloud app development on Atlassian. ✨ Ever heard the term Atlassian ecosystem and wondered just exactly what it meant? Grab a cup of ☕ and join ...

57 views 0 2
Read article

Community Events

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

Events near you