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.
Have you been looking for a solution to easily create Confluence pages directly from a Jira Cloud issue? The no code solution is here with the brand new app Elements Publish to Confluence, which work...
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