Duplicate entity handling CSV gets stuck in UI

XMLWordPrintable

    • 2
    • Minor
    • 2

      Issue Summary

      When using the Duplicate Entity Handling Early Access Program, custom field schemes with empty values could prevent CSV generation from occurring.

      Note: This currently requires enrollment in an Early Access Program.

      Steps to Reproduce

      1. Create a Jira Migration through JCMA.
      2. Run the preflights
      3. The generation of the CSV to manage duplicate entity handling appears to get stuck at 7%.

      Expected Results

      An error should be presented with information on how to correct the error to the Jira administrator running the migration.

      Actual Results

      The below exception is thrown in the atlassian-jira-migration.log file:

      [c.a.j.m.preflight.reports.DuplicateEntitiesReportService] Failed to generate duplicate entities report for execution ID 47d29e35bf464b6a9d7741dfae6341d94d8afaf2
com.atlassian.jira.migration.httpclient.exceptions.HttpProtocolException: An error occurred attempting to deserialize to com.atlassian.jira.migration.httpclient.PaginatedEntityListResponse<com.atlassian.jira.migration.duplicates.configOnly.CustomFieldScheme>
...
Caused by: com.fasterxml.jackson.module.kotlin.MissingKotlinParameterException: Instantiation of [simple type, class com.atlassian.jira.migration.duplicates.configOnly.CustomFieldScheme] value failed for JSON property description due to missing (therefore NULL) value for creator parameter description which is a non-nullable type
 at [Source: REDACTED (`StreamReadFeature.INCLUDE_SOURCE_IN_LOCATION` disabled); line: 1, column: 310] (through reference chain: com.atlassian.jira.migration.httpclient.PaginatedEntityListResponse["values"]->java.util.ArrayList[1]->com.atlassian.jira.migration.duplicates.configOnly.CustomFieldScheme["description"])

      Workaround

      The data causing the issue can be from either Jira Data Center or Jira Cloud.

      For the Data Center records, you can identify the records that are causing the error with the following SQL and then adding a description in the UI:

      select * from fieldlayoutscheme where description is NULL;

      If the error remains after correcting the Data Center records, please open an ticket with Atlassian Support so we can investigate the records in Jira Cloud.

            Assignee:
            Unassigned
            Reporter:
            Eli Boaz [Atlassian Support]
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated: