Supported Atlassian apps and types of links
This page explains what Atlassian apps and types of links you can update.
Supported apps and migration types
Here’s a summary of what’s supported.
Atlassian apps
Jira applications
Confluence
Migration type
From Data Center to Cloud
Between Cloud sites
Federation: Jira Data Center
When you split a single Jira Server or Data Center instance into multiple instances in cloud, issue links that were previously local will no longer exist. You can recreate them as remote links and update to their new destinations. This is supported only with REST API. Learn how to update links to federated instances
You can recreate your links only for 2 weeks after the migration. Afterwards, the migration data that we sue to identify those links is deleted for privacy reasons.
Limitations and recommendations
Here is some important information:
You can only update links between cloud apps within one organization. If your apps are on multiple sites, but still within one org, this is supported.
When updating links from Jira to Confluence, we recommend that you do it only after you’re sure that your Confluence migration (partial or full) was successful, and you won’t have to delete and re-migrate any data. Many Confluence links are updated based on IDs (not just replacing URLs), so they will be different after every re-migration of the same data. When you re-migrate, the previously updated links in Jira keep using the old IDs and can’t be updated again to the new ones.
Types of links
We fix the majority of Jira and Confluence links, with some exceptions. You can review the list below for more details and examples of links.
In Jira applications
Type | Sample links |
---|---|
Jira-specific | |
Links to Jira work items (local and remote) |
|
Links to Jira work items in user-generated content (description, comments) | |
Jira source site URLs in the content added by users |
|
Links to boards and backlogs |
|
Local links that become remote links after splitting an instance in cloud (federation) | - |
Links to Jira attachments |
|
Confluence-specific | |
Links to Confluence pages |
|
Links to Confluence pages in user-generated content, including TinyURLs and blog posts | |
Links to Confluence blogs |
|
Links to Confluence that use the following URL (usually, this includes links to the space’s main page) |
|
Links to Confluence attachments |
|
Jira Service Management-specific | |
Links to service projects and requests (local and remote) |
|
Links to customer portals |
|
Links to queues |
|
Links to customers and notification logs |
|
Unsupported links |
---|
|
In Confluence
Type | Sample links |
---|---|
Confluence-specific | |
Base URL |
|
Links to spaces |
|
Links to pages |
|
Links to blogs |
|
Links to attachments |
|
Links to thumbnails |
|
Outgoing links in Page information | - |
Macros:
| - |
Jira-specific | |
Base URL |
|
Links to Jira work items |
|
Links to boards and backlogs |
|
Jira Service Management-specific | |
Links to service projects and requests (local and remote) |
|
Links to customer portals |
|
Links to queues |
|
Links to customers and notification logs |
|
Unsupported links |
---|
|
Next steps
When you’re ready, start updating your links. Learn how to update links after migration
Was this helpful?