nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Status Summary for Jira Project is now showing correct totals...

Kevin Murphy8

One of our Projects which uses the "New" issue type (instead of Open for the default issue type) is showing an incorrect total when looking at the Status Summary.

If I click on "New" it shows 16 issues, which is correct but here it's showing 1544. This is likely lumping the "Closed" issues in with the new. Any ideas why this is occuring?

Accepted answers

All comments

Nic Brough -Adaptavist-

Looks like it could be an indexing issue. We can confirm or disprove that by re-indexing.

If it is that, the report should be corrected afterwards, and you'll need to start looking into what is/was causing the index to go awry. If it's not, then we'll have to dig into the issues and look at their histories and data. But try re-indexing first, or we could go running off in totally the wrong direction

Kevin Murphy8

1/2 way through re-indexing (started it a few hours ago actually). Made a change to one of the transition conditions (POST). Seems like it's an issue with the Workflow. Will update once it's done.

Nic Brough -Adaptavist-

That makes a lot of sense - if there's an issue with a transition, then your raw data should be fine, but the index drifts off in certain cases. If re-indexing fixes it, then this is probably the problem.

Kevin Murphy8

No luck - removed one of the conditions from one of the oft used transistions and re-indexed. No luck. Same Status Summary #'s. Any other ideas? Like to keep the work flow intact (and no apply a new/default workflow).

Kevin Murphy8

When I click on new the Filter is as follows:

project = PWET AND status = New ORDER BY priority DESC

This shows 17 issues (same as when I click on "New" in the Status Summary. Doing a search search for stauts = Closed brings up 1,522 slips. 17+1522 = 1539, the total shown in the Status Summary (some change since the screenshot above). Should note I'm still not seeing any Closed slips in the Status summary.

Should note I'm free to "break" things here as this is a development instance (not our proudction server).

You'll notice that now there is a "Final Review" count of 1. Going to remove all the POST instructions that clear the Resolution field for anything transitioning to the Close status and re-index.

Let you know what happens. If I don'get results I'll poke around on some of the slips like you suggested (looking at it's history).

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira

jira-administration