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:
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
As part of the Bitbucket product team I'm always interested in better understanding what kind of impact the use of our tools have on the way you work. In a recent study we conducted of software devel...
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