Incorrect link redirection from Jira Sandbox to Confluence Prod after project migration INX

[Team Support bit2bit Americas]

Hi team,

We recently performed a migration of a project and its documentation from Production to Sandbox, and we are experiencing an issue with the integration links between Jira and Confluence.

Project Name: INX Jira Source: Production Jira Destination: Sandbox (clarocenam-sandbox.atlassian.net) Confluence Source: Production Confluence Destination: Sandbox (Contains the RCA documentation for INX)

The Issue: The bidirectional linking is partially broken:

1. Confluence Sandbox to Jira Sandbox (WORKS): When we are in Confluence Sandbox and click the Jira link inside the RCA page, it successfully takes us to the correct ticket in Jira Sandbox.

2. Jira Sandbox to Confluence (FAILS): When we are inside a ticket in Jira Sandbox and click the linked Confluence page, instead of redirecting us to Confluence Sandbox, it redirects us to Confluence Production.

What we have tried so far: We tried using the Link Fixing tool to update the URLs, but the behavior remains the same. The Jira tickets in Sandbox keep pointing to Confluence Production.

Steps to reproduce:

1. Go to Jira Sandbox (clarocenam-sandbox.atlassian.net) and open a migrated ticket from the INX project.

2. Click on the Confluence page link attached to the ticket under Confluence pages or Remote links.

3. Notice that the URL opens Confluence Production instead of Confluence Sandbox.

Expected behavior: The link in Jira Sandbox should point to the migrated RCA page in Confluence Sandbox.

Could you please help us understand why the Link Fixing tool didn't apply to these remote issue links, or how we can update the Cloud AppLinks or Workspace IDs for these migrated tickets?

Thank you!

[Arkadiusz Wroblewski]

Hello and welcome to Atlassian Community @Team Support bit2bit Americas 

Before I send you wall of text some "Food for Thoughts" 

https://support.atlassian.com/migration/docs/examples-and-use-cases-for-updating-product-links/ 

This is due to a sandbox limitation where cross-product links point to the production version, so a manual workspace ID change won't fix it.

If you think about it, it makes sense. It's copy.

I know there's some optimization planned for Sandbox, but I don't know the exact details.

First, please confirm that the pages actually exist within your Confluence sandbox.

Run the Jira link-fixing tool in sandbox mapping the production Confluence URL to the sandbox URL. If links were skipped or failed (often due to independent space refreshes), contact Atlassian Support for backend mapping fixes. 

Best,

Arkadiusz 🤠