Issue Summary

Releasing a version and moving unresolved work items to another version updates the "Fixversion" field history in the incorrect order

Steps to Reproduce

1. Create a Jira space and create a version A
2. Create a work item 1 and add it to the newly created version A
3. Create a new version B
4. Release version A while work item 1 is unresolved. Move the unresolved work item to version B
5. Check the history of work item 1.

Expected Results

The work item history should capture the list of events related to Fix version field as expected:

1. Fixversion field changed from None to Version A
2. Fixversion field changed from Version A to None
3. Fixversion field changed from None to Version B

Actual Results

The Fixversion field value change history on the ticket is out of order:

1. Fixversion field changed from None to Version A
2. Fixversion field changed from None to Version B
3. Fixversion field changed from Version A to None

Workaround

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