Issue Summary

When migrating a JSM project that uses multiple request types and one( or multiple) request types are in the below situation ( all conditions to be met), the migration will fail for all request types, as the whole batch fails and more than this, the issues are not migrated.

Migrator will notice the following error in the import logs:

2024-10-10 19:41:28 +0000	ERROR	jira/servicedesk	requestType	DefaultEntityMigrationError	Chunk Migration Error	Chunk Migration Error: DefaultEntityMigrationError(dateTime=2024-10-10T17:56:36.980007771Z, entityId=mri:mig:jira/servicedesk:requestType:xxxxxx, reason=400 The given input default value type is invalid, actionToResolve=null, numDownstreamFailures=30245, severity=ERROR)

If the below conditions are met ( all of them) on at least one of the request types the import will fail for the whole batch and consequently the issues will not be migrated:

1. Non-empty "defaultValues" list
2. "required" = true
3. "cfValue" = null
4. "value" = null OR "fieldName" = null

This is reproducible on Data Center: (yes)

Steps to Reproduce

1. Step 1
   Create JSM project with request types and on one of the request types add a required field with a non empty default value in which "cfValue" is null and "value" or "fieldName" is null .
2. Step 2
   Migrate the JSM project S2C

   Expected Results

   Data preparation checks to capture this inconsistency and do not allow the migrator to proceed. More than this, even if not fixed, the rest of the batch should be migrated.

Actual Results

Data preparation check is green but the migration will fail during import with the aforementioned error log. Not only it will fail the problematic request type, it will fail the whole batch of request types.

Workaround

Contact Atlassian support to check the export file and provide you the request types that are inconsistent. After the problematic request types are identified, migrator can remove the field or can add proper default values.