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,552,866
Community Members
 
Community Events
184
Community Groups

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.

0 comments

Comment

Log in or Sign up to comment
TAGS
AUG Leaders

Atlassian Community Events