Resolved field is empty in issue navigator but not in issue

[maschle]

Hi all

we have a problem with the resolved field in the issue navigator.

This filter returns issues but it shouldnt?

status in (Closed, Resolved) and resolved is EMPTY

The resolved field is empty in the issue navigator and when we click on an issue the resolved field is actually set.

So it seems that the index and the database are out of sync. Doing a re-index only helps temporarily.

The tickets which are returned by this filter are getting progressively  more. The strange thing is that even very old issues are returned by this filter (which have not been modified/updated). So there shouldn't be a problem with the postfunctions. 

Can someone help us?

[Vasiliy Zverev]

It seems that resolution is set but with no reindex. Try to investigate workflows for such cases.

[maschle]

Is there a service running which checks all tickets periodically? If I do a manual "background re-index" the "fixed" tickets should stay consistent but they don't?

[Nic Brough -Adaptavist-]

No, there's no service to do that.   Issues are indexed individually on every change

The indices break in several ways

1. A system incident - ranging from a hard shutdown or physical problem down to minor glitches or simply being overloaded, something not part of JIRA interrupts the index process.  This doesn't happen a lot, but if you are seeing performance issues, one side effect is sometimes indexing failure
2. Bugs in the core - rare, and usually fixed quickly when it's an indexing thing, but bugs in the core product do happen
3. Bad or broken add-ons
4. Badly configured add-ons

There's no regular service because 1 and 2 are edge cases that can't be caught, and 3 and 4 are by far the most common cause of indexing issues.