Summary

Learn what to do when the Assess your apps option is missing in your migration assistant home:

Overview

There are two reasons main reasons for this behaviour:

Invalid email address

This issue can happen when the user account trying to assess the apps doesn't have an email address, even if the user account is a Jira system administrator.

You can see the below message in the application log file atlassian-jira.log:

/rest/migration/latest/mas/event/ui [c.a.cmpt.crypto.BcryptAnalyticsEmailHasher] Malformed email addressjava.lang.IllegalArgumentException:
 Malformed email address. Does not contain only one mandatory symbol @

Therefore, the user trying to assess the apps must have a valid email address. This is also a pre-requisite for migrating users and would later show up in the migration showing an error of invalid email address. 

We're tracking this behavior on the following bug report:

• MIG-1360 - Getting issue details... STATUS

Database inconsistency (Jira only)

This issue can happen when there are inconsistencies in the AO_6FF49D_ANALYTICS_EVENT_pkey table.

You can see the below log signature in the application log file atlassian-jira.log:

org.postgresql.util.PSQLException: ERROR: duplicate key value violates unique constraint "AO_6FF49D_ANALYTICS_EVENT_pkey"
Detail: Key ("ID")=(NN) already exists.
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:

Solution

Based on the scenario identified in the section above:

Invalid email address

The recommendation is to follow the instructions from the document below:

• Resolve invalid email addresses when migrating to the Cloud

Database inconsistency (Jira only)

1. Execute the below queries to confirm if the last_value column is smaller than the MAX("ID"):

   SELECT MAX("ID") FROM "AO_AEFED0_USER_INDEX";
   SELECT last_value FROM "AO_AEFED0_USER_INDEX_ID_seq";
   SELECT MAX("ID") FROM "AO_6FF49D_ANALYTICS_EVENT";
   SELECT last_value FROM "AO_6FF49D_ANALYTICS_EVENT_ID_seq";

2. If the value from last_value column is smaller than the value of the column MAX("ID"):
   1. Stop the Jira On-Premise instance.
   2. Take a full backup of your database.

   3. Run the following SQL queries in the Jira On-Premise database:

      SELECT setval('"AO_6FF49D_ANALYTICS_EVENT_ID_seq"', MAX("ID")) FROM "AO_6FF49D_ANALYTICS_EVENT";
      SELECT setval('"AO_AEFED0_USER_INDEX_ID_seq"', MAX("ID")) FROM "AO_AEFED0_USER_INDEX";

   4. Start the Jira On-Premise instance.
   5. Run a full reindex in the Jira On-Premise.
3. If the value from last_value column is greater than the value of the column MAX("ID"), you will need to open a support ticket to investigate this issue.