Uploaded image for project: 'Atlassian Cloud'
  1. Atlassian Cloud
  2. CLOUD-11612

Improve error logging for C2C migrations

XMLWordPrintable

    • 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.

    • Jira Software, Jira Service Management, Jira Work Management

      Issue Summary

      When a C2C migration fails, there is no error detail shown in the browser UI. It would be helpful if customers can see where the issue lies as often it may result in fixing it before contacting Atlassian Support.

      An example is failure of a migration due to dependencies such as issue types for boards. Once the message was found by Support and share with the customer, the issue was resolved. However, no message or error was shown to the customer in the UI upon failure.

      This is reproducible on Data Center: not applicable

      Steps to Reproduce

      1. Run a Cloud to Cloud migration of Jira Projects
      2. Migration either shows failed or incomplete status
      3. No error or message shows up in the browser to indicate where the issue may lie

      Expected Results

      An error or message showing what could've caused the migration to fail can help the customer to avoid contacting Atlassian Support just to understand what has gone wrong with the migration.

      Actual Results

      No error or mesage is shown in the UI when a migration fails. As opposed to a server-to-cloud migration where application logs may have some clues, the customer has no way of determining what went wrong except contact Atlassian Support.

      Workaround

      Customer must contact Atlassian Support.

            Unassigned Unassigned
            kplaha Kanwar
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: