Uploaded image for project: 'Migration Platform'
  1. Migration Platform
  2. MIG-1177

Server to cloud project to project migration does not set correct default project language

    • 2
    • Minor
    • 1

      Issue Summary

      Project to project migration from server to cloud does not set the correct project default language.

      Steps to Reproduce

      1. Target cloud site: set instance default language differently from server project default language. Eg: Project default is English UK, cloud instance default is the English US.
      2. Perform project to project migration.

      Expected Results

      Migrated project default language set to English UK.

      Actual Results

      Migrated project default language set to cloud instance default, the English US.

      Workaround

      Set cloud instance default language to English UK.

          Form Name

            [MIG-1177] Server to cloud project to project migration does not set correct default project language

            Atlassian Update - November 30, 2023

            Hi Everyone,

            Thank you for previously raising this bug and bringing it to our attention.

            With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base.

            With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time.

            If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue.

            We appreciate your understanding and look forward to providing you with an enhanced migration experience.

            Thank you again for providing valuable feedback!
            The Migrations team

            Mark Tunmer added a comment - Atlassian Update - November 30, 2023 Hi Everyone, Thank you for previously raising this bug and bringing it to our attention. With the release of Jira Cloud Migration Assistant (JCMA) 1.7.3 on September 12th, 2022, and our ongoing commitment to improving our product, we have transitioned to a new code base. With this ticket having been logged before the changeover date/JCMA version, we believe it’s no longer relevant to the current code base. Bearing that in mind and continuing the culture of being honest and open, we have taken the decision to close this bug at this time. If you feel this bug is still impacting your team, please let us know through the Migration Support channel and we will revisit the issue. We appreciate your understanding and look forward to providing you with an enhanced migration experience. Thank you again for providing valuable feedback! The Migrations team

              Unassigned Unassigned
              vtruong Vu 🎧
              Affected customers:
              3 This affects my team
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: