Issue Summary

The field 'Start date' is created as a locked field OOTB. In the rare situation where this field does not exist in the destination site for whatever reason, it is then created during a migration. When the migration created this field, it was created as unlocked.

This will work fine on the first migration however subsequent migrations will fail in this field as the states don't match.

Steps to Reproduce

1. Create a destination site that does not have the 'Start date' field present
2. Migrate into this site with a project that has issues using the 'Start date' field.
3. Observe the 'Start date' field is created in the destination.
4. Delete the migrated project.
5. Migrate the same project again or another project.
6. Observe the failure.

Expected Results

The 'Start date' field is created as a managed, locked field in the destination and any subsequent migration doesn't fail.

Actual Results

The field is created as unlocked and any subsequent migrations fail.

The below exception is thrown in the migration logs:

ERROR	Chunk Migration Error: DefaultEntityMigrationError(dateTime=2023-10-24T18:23:14.537149Z, entityId=mri:mig:jira/classic:customField:10703, reason=Cannot find a locked custom field with name Start date and type com.atlassian.jira.plugin.system.customfieldtypes:datepicker, actionToResolve=null, numDown... 

Workaround

Reach out to Atlassian support to lock the field in the destination.