We couldn't load all Actvitity tabs. Refresh the page to try again.
If the problem persists, contact your Jira admin.
IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1499

Post Migration Link Fixing should be able to address multiple source URLs

    • Icon: Suggestion Suggestion
    • Resolution: Unresolved
    • None
    • Fixing Broken Links
    • None
    • 44
    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      User Problem

      When migrating from DC to Cloud, it is expected that links will be broken. The following KB outlines the process for handling this situation: After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance

      It is possible that the source environment has changed its URL multiple times throughout the environment's history.

      Suggested Solutions

      Please provide a way to perform link fixing that captures all source URLs.

      Source URL Destination URL
      http://source.jira.server https://<cloudsite>.atlassian.net
      https://source.jira.server https://<cloudsite>.atlassian.net
      https://newsource.jiraserver.com https://<cloudsite>.atlassian.net

      Links should be fixed based on the source URLs and updated to the new destination URL.

      Current Workaround

      None at this time. Only the current source URL can be used to perform link fixing.

            Loading...
            IMPORTANT: JAC is a Public system and anyone on the internet will be able to view the data in the created JAC tickets. Please don’t include Customer or Sensitive data in the JAC ticket.
            Uploaded image for project: 'Migration Platform'
            1. Migration Platform
            2. MIG-1499

            Post Migration Link Fixing should be able to address multiple source URLs

              • Icon: Suggestion Suggestion
              • Resolution: Unresolved
              • None
              • Fixing Broken Links
              • None
              • 44
              • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

                User Problem

                When migrating from DC to Cloud, it is expected that links will be broken. The following KB outlines the process for handling this situation: After a successful Server to Cloud Migration, URL links are broken in the new Cloud instance

                It is possible that the source environment has changed its URL multiple times throughout the environment's history.

                Suggested Solutions

                Please provide a way to perform link fixing that captures all source URLs.

                Source URL Destination URL
                http://source.jira.server https://<cloudsite>.atlassian.net
                https://source.jira.server https://<cloudsite>.atlassian.net
                https://newsource.jiraserver.com https://<cloudsite>.atlassian.net

                Links should be fixed based on the source URLs and updated to the new destination URL.

                Current Workaround

                None at this time. Only the current source URL can be used to perform link fixing.

                        Unassigned Unassigned
                        asalinasii@atlassian.com Alfonso S.
                        Votes:
                        3 Vote for this issue
                        Watchers:
                        14 Start watching this issue

                          Created:
                          Updated:

                            Unassigned Unassigned
                            asalinasii@atlassian.com Alfonso S.
                            Votes:
                            3 Vote for this issue
                            Watchers:
                            14 Start watching this issue

                              Created:
                              Updated: