When we update a Confluence page that is linked to a Jira issue and add any Jira issue URL, it creates a RemoteWorkItemLink update entry in the issue’s history and updates the issue’s “Updated” timestamp. Changes to remote link metadata should not update the issue’s updated date.

When a Confluence page containing a Jira Smart Link or Jira Issue Macro is autosaved (Live Doc behavior), Confluence triggers a remote link update in Jira. This results in a RemoteWorkItemLink entry in the Jira issue's change history.

The change is attributed to whichever user is currently active on the Confluence page during the autosave, even if they have not modified the link or the page content. This behavior corrupts the Jira updated timestamp and creates false audit trails in the issue history.

Remote link updates pollute updated-based reports and dashboards, falsely marking issues as "recently updated" without meaningful work.

Attaching video for reference

Steps to Reproduce

1. Create a Confluence page and insert a Smart Link to a Jira issue (e.g., ABC-123).

1. Have User A view or edit the page.

1. Have User B simultaneously view the same page.

1. Wait for a Confluence autosave/draft sync event to trigger.

1. Check the Change History of the Jira issue (ABC-123).

Expected Results

Autosave events should not trigger a remote link update in Jira unless the link itself has been modified or the page has been explicitly published. The Jira updated field and history should remain unchanged during background draft syncs.

Actual Results

Jira records a RemoteWorkItemLink update. The history entry attributes the change to the user present during the autosave (e.g., User B), and the Jira issue's updated timestamp is refreshed, causing it to appear in JQL queries like updated >= -30d.