Issue Summary

When the Components field is updated, such that there are multiple(or single) entries added or removed, the issue history entries don't 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., 2025 and 2026.
3. Create a ticket and update the Components field with 2025.
   • The history entry shows None -> 2025 (which is correct)
4. Update the Components field with 2026 (now, the field contains 2025 and 2026)
   • The history entry shows None -> 2026 (which is incorrect because the field was not empty. It should reflect 2025 and 2026 as a single event/changelog)
5. Remove component 2025 from the Components field, so that only 2026 is present
   • The history entry shows 2025 -> None (which is incorrect because 2026 is still present)
6. Remove the version 2026 from the Components field so that the field is now empty
   • The history entry shows 2026 -> None (which is correct because the field is now empty)

Expected Results

The work item history entries should reflect previous/current values that were/are present in the Components field.

Actual Results

The work item history entries don't capture the previous/actual values of the Components field within a single event/changelog.

Workaround

Not available. A workaround will be added here once available.