Reindex problem in workflow transition

[Roger Ares]

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.

[Radu Dumitriu]

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:

https://jira.atlassian.com/secure/IssueNavigator.jspa?sorter/field=created&sorter/order=DESC

[Gisela]

Rares, I m having the same problem, do you discover anything?

I found the issue https://jira.atlassian.com/browse/JRA-29424, I think maybe is releated.

[Harry Chan]

Do you know what do you have in your post functions? Check if the order is correct and it is indexing there.

[Tomáš Štalmach]

Hey,

Did someone figured out how to fix this issue?

We have same problem after 3 years of publishing this question.