So, if I understand correctly, we practically need to locate the broken workflow linked with that issue somewhere and add this post function "Re-index an issue to keep indexes in sync with the database." ? Am I misunderstanding something, or is there a way to figure out which issue has to do with the inconsistency?
We had the same issue when we added our custom code to Jira which threw NullPointerException(NPE). In this case the reindexing did not take place and lucene index was inconsistent. Maybe it is your case as well, look for NPE in the atlassian-jira.log.
Actually this situation could be caused by any unhandled exception in a custom code which try to create or modify issue.
In the past, Portfolio for Jira required a high degree of detail–foresight that was unrealistic for many businesses to have–in order to produce a reliable long-term roadmap. We're tur...
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