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

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 vote

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
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Published Thursday in Confluence

Three common content challenges + how to manage them

An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough   cough, all companies). If content calendars, marketing plans, and bu...

96 views 0 6
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you