Changing Sprint on issue doesn't always reflect the change on the Board on other Data Center nodes

Issue Summary

Changing Sprint on issue doesn't always reflect the change on the Board on other Data Center nodes.

Steps to Reproduce

1. Create 2 parallel sprints and start the sprints
2. Assign some issues to both of these sprints
3. Open one issue and change sprint (e.g. from Sprint 1 to Sprint 2). This change is instantly visible on the Board on the originating node
4. Open the same board on other DC node and see the results

Expected Results

On the Board on the other DC node, the change is reflected (issue assigned from Sprin 1 print to Sprint 2)

Actual Results

The issue doesn't get assigned to the new sprint (Sprint 2), however, the issue gets removed from the old sprint (Sprint 1).

• Switched AG-2 issue to Sprint 2. Visible on originating node 1:
  
• On node 2, we can see the issue removed from Sprint 1, but it is not added to Sprint 2:
  
  

Workaround

Update the affected issue, this will update the index and the issue will become visible in the assigned sprint.

Notes

• Index statistics fetched from the REST endpoint:

  {"nodeId":"jira2","reportTime":"2020-04-30T10:44:58.906+0000","issueIndex":{"indexReadable":true,"countInDatabase":5,"countInIndex":4,"countInArchive":1,"lastUpdatedInDatabase":"2020-04-30T10:40:53.336+0000","lastUpdatedInIndex":"2020-04-30T10:40:53.000+0000"},"replicationQueues":{"jira1":{"lastConsumedOperation":{"id":10300,"replicationTime":"2020-04-30T10:40:13.629+0000"},"lastOperationInQueue":{"id":10300,"replicationTime":"2020-04-30T10:40:13.629+0000"},"queueSize":0}}}
  

  {"nodeId":"jira1","reportTime":"2020-04-30T10:45:19.064+0000","issueIndex":{"indexReadable":true,"countInDatabase":5,"countInIndex":4,"countInArchive":1,"lastUpdatedInDatabase":"2020-04-30T10:40:53.336+0000","lastUpdatedInIndex":"2020-04-30T10:40:53.000+0000"},"replicationQueues":{"jira2":{"lastConsumedOperation":{"id":10221,"replicationTime":"2020-04-30T10:40:53.367+0000"},"lastOperationInQueue":{"id":10221,"replicationTime":"2020-04-30T10:40:53.367+0000"},"queueSize":0}}}
  

• Issue is not reproducible on Jira 8.5.3.