When changing custom field while transitioning or creating a ticket, wrong value is put to the index

Issue Summary

Changes done to the ticket are not reflected in the index - JQL query. 

For example: There is a Select List (single choice) custom field “xyz”. When there are changes to it, they are reflected in the issue details screen but not in the JQL query result.

The problem cannot be reproduced every time.

Steps to Reproduce

1. Transition an issue within the project which uses A4J/Slack and updates a Select List (single choice)  field with a new value.
2. Search issue against the custom field.

    key =xyz-1234 and cf[10000] is not empty 

Expected Results

The value and the details screen and in the JQL search are the same every time.

Actual Results

The value on the details screen is correct. The JQL search shows the wrong value. 

Workaround

Currently, there is no known workaround for this behaviour. A workaround will be added here when available