Linking issues with remote link creates duplicate history entries

Issue Summary

Linked issues using application links create duplicate entries in the issue history tab.

This is reproducible on Data Center: Yes

Note tha this unexpected changelog may show up a long time after the creation of the remote issue link - several months in some cases.

• This entry can be seen on changegroup/changeitem tables and the "last updated date" gets updated as well.
• This can lead to inconsistencies in reporting since the "last updated date" will not reflect the last valid update on the issue.

It could not be reproduced on 9.0.0 or older.

Steps to Reproduce

1. Create application links between Jira instances with versions >=9.1.0
2. Create a Jira issue, and link to an issue on a different Jira instance using the application link.
3. Change the status of the linked remote issue.

Expected Results

Only one entry in the history tab to be seen with the remote link:

Actual Results

A new entry with original and new values set to the same issue link is added to the issue history.this entry is added every time the remote issue is transitioned to a new state or a new user tries to make the new remote link.  this behaviour is causing flooding of the issue history. and in turn causing inconvenience for customers to identify real change.

Workaround

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