Inconsistency between number of Completed Issues in the Epic Report and Issue Navigator
Platform Notice: Cloud and Data Center - This article applies equally to both cloud and data center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
Problem
The Epic Report are not showing the right number of completed Issues compared to what being shown after clicked on the "View in Issue Navigator" of that report screen.
For example : In the Completed Issues section of the Epic Report, it would be showing less numbers of Completed Issues (eg:4).
However when user click on the "View in issue navigator" link of that Epic report , it will show more number of Completed Issues(eg:14)
Diagnosis
Environment
JIRA 7
Diagnostic Steps
Check and compare between the Configuring Filters and the Viewing the Epic Report (View in Issue Navigator) for the completed issue.
Cause
The Configuring Filters automatically filters out those tasks which is are not relevant to the current sprint.
Solution
Workaround
For example: The query Configuring Filters will includes a clause to limit the results to current sprint .
1
project = SUPP AND issuetype in (task, epic) AND (Sprint in openSprints() AND resolution = Unresolved) ORDER BY Rank ASCAfter removed the "Sprint in openSprints() AND resolution = Unresolved" clause from the query, the user will be able to see correct number of completed Issues in the Epic Report.
1
project = SUPP AND issuetype in (task, epic) ORDER BY Rank ASCWas this helpful?