Jira Macro Repair tool is not able to pick the correct source applink/ServerID if the source applink is already existing on target cloud

XMLWordPrintable

    • 1

      Problem Definition

      The customer was running a C2C cloud migration from source site A to target site B. However, it's not able to pick the correct appID as source to fix when running the JMR on target site B after the migration.

      Situation

      The customer was running a C2C cloud migration from source site A to target site B.

      Before the migration, the application link was already created and set as primary:

      Applink on target B linked to source A

      After the migration, when running the JMR, the AppID needs to be fixed, only showing on target site list. However, it should show up on the source site list which is to be fixed.

      Even customer removed the applink, the JMR still can't present the correct source site appID.

      Suggested Solution

      • This seems to be a potential bug as the appID was not read correctly.

      Workaround

      Need support team to run a JMR script to fix all the serverID which is not the target cloud site one.

              Assignee:
              Unassigned
              Reporter:
              Tian Zeng
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: