JCMA v1.12.23 repeatedly throws "Error Communication with Server" error during Migration Validation check which results in a never ending loop during pre-checks.

XMLWordPrintable

    • 4
    • Severity 2 - Major
    • 8

      Problem Statement:

      User is running the latest version of JCMA 1.12.23 and when they try to Assess their users, they get "Invalid Emails" and "Duplicated Emails" validation failures for which they cannot select the "Migrate invalid users as Former users".

      How to Reproduce:

      • Install / upgrade the latest version of JCMA 1.12.23 (relative to the time when this BUG was opened).
      • You would need to have some invalid emails and duplicated email accounts on the Jira Server instance.
      • Try to Assess the users, We get "Invalid Emails" and "Duplicated Emails" validation failures for which we cannot select the "Migrate invalid users as Former users".
      • When they select the above option, it gives them the
        We couldn't save your changes - A migration is currently in progress. Once it's done, you'll be able to apply your changes
      •  Verify on the UI and the DB, there is no migration running currently.
      • Next, we used the "Update users based on CSV file" option. We provide valid email address and it fixed the validation part, but again the below error pops up in the left bottom corner of the UI.
        Error Communicating with Server
      • Moving forward when they Click on "Done", it gives them the next page where it pops up in the left bottom corner with the message. 
        Your Users are ready to migrate to Cloud - Select Create a migration to create a new migration plan
      • When they create the Migration Plan, it again shows the "Invalid email addresses" and "Duplicated email accounts" with the same user count as before and the process of fixing the Invalid Users starts all over again.
      • This goes on in Loops and the Invalid Emails and Duplicated Emails are never fixed. Seems like a problem only with the version 1.12.23.

      Attached some screenshots for context

      Solution:

      • Download the JCMA 1.12.22 or 1.12.21 from Jira Cloud Migration Assistant Versions
      • Install one of the above versions on the Jira Server
      • Downgrading to these versions and then creating a "New Migration Plan" solves the issue and the Migrations is successful.

        1. Screenshot 2025-02-15 at 14.53.35.png
          431 kB
          Vaibhav Revankar
        2. Screenshot 2025-02-15 at 14.55.59.png
          308 kB
          Vaibhav Revankar
        3. Screenshot 2025-02-15 at 14.57.30.png
          64 kB
          Vaibhav Revankar
        4. Screenshot 2025-02-15 at 14.59.27.png
          194 kB
          Vaibhav Revankar
        5. Screenshot 2025-02-15 at 15.02.04.png
          479 kB
          Vaibhav Revankar

            Assignee:
            Unassigned
            Reporter:
            Vaibhav Revankar
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: