We have an issue in a state A and we promote the workflow manually changing this state to B. While the status showed in the view screen of the issue is B, when we execute a JQL searching this particular issue the result is status = A. Then, doing a full reindex of the platform, this problem is solved and the statuses are the same in both sides.
So, it is a clear evidence that the indexes are not updated properly during the transition of the workflow. We would like to know the behaviour of Jira when we have custom workflow post-functions that reindex the issues, and also the effects that can have a scheduled task that is changing some fields of the same issues that are affected by the workflow's transitions.
Do you know where can be the problem? This has happened in 4 out of 1200 issues.
Let me know if you need more details.
Thanks a lot.
I think that you should open up a bug and include the logs: https://jira.atlassian.com/browse/JRA This may be related to lucene, not Jira or to the plugins firing up on the transitions (if any), but check first the opened bugs:
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
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot