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?
No, there's no service to do that. Issues are indexed individually on every change
The indices break in several ways
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.
I have multiple projects that use variations of the same base workflow. The variations depend on the requirements of the project or issue type. The variations mostly come in the form of new statuses ...
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!
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