Issue history entries for Affects versions and Fix versions fields are misleading

Issue Summary

When the Affects versions and Fix versions fields are updated such that there are multiple entries added or removed, the issue history entries do not capture the correct values that are present in the field. The history entry is updated with 'None -> XXXX' or 'XXXX -> None' which is misleading and confusing for the user.

Steps to Reproduce

1. Create a Jira Software project
2. Create two different versions. For e.g.; 1.0 and 1.1
3. Create a ticket and update the Affects versions field with 1.0
   • The history entry shows None -> 1.0 (which is correct)
4. Update the Affects versions field with 1.1 (now, the field contains 1.0 and 1.1)
   • The history entry shows None -> 1.1 (which is incorrect because the field was not empty. It should ideally show 1.0 and 1.1)
5. Remove the version 1.0 from the Affects versions field so that only 1.1 is present
   • The history entry shows 1.0 -> None (which is incorrect because 1.1 is still present)
6. Remove the version 1.1 from the Affects versions field so that the field is now empty
   • The history entry shows 1.1 -> None (which is correct because the field is now empty)

Expected Results

The issue history entries should still show the remaining values that are present in the Affects versions or Fix versions field instead of showing 'None'

Actual Results

The issue history entries do not capture the existing values of the Affects versions or Fix versions field.

The REST API changelog endpoint also does not capture the remaining values in the fields.

Workaround

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