Overall requirement coverage incorrectly showing no of issues in each requirement status

Aswini Vayyala September 20, 2016

Hi,

I have an 'Overall Requirement Coverage' gadget that is incorrectly showing the no of issues in each requirement (Eg: wrong no of issues in 'not run', wrong no of issues in 'uncovered')

When I run the filter I can clearly see the no of issues in 'not run' and 'uncovered' status is far different.

The following is the filter used with test data:

 

"Epic Link" in (epiclink1,epiclink2,...,epiclinkn) AND fixVersion in ("fixVersion1", "fixVersion2") AND labels != testLabel ORDER BY Rank ASC

 

Can anyone help me understand why is the difference in the number of issues?

1 answer

0 votes
Nic Brough -Adaptavist-
Community Leader
Community Leader
Community Leaders are connectors, ambassadors, and mentors. On the online community, they serve as thought leaders, product experts, and moderators.
September 20, 2016

Could you explain what the "overall requirement coverage" gadget is?  Is it a standard "filter results" or "filter statistics" gadget, or is it something provided by an add-on (x-ray)?

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events