Issue status duplication (To Do) leading to config drift and migration failure.

Issue Summary

Issue status duplication due to server side configuration change. This leads to migration failures.

Steps to Reproduce

1. By default the issue status on the server, 'To Do', is mapped to the category 'To Do'. (Status Category number 2).
2. On cloud the status, 'To Do', doesn't exist by default.
3. I migrate a project for the first time to the cloud instance and this leads to creation of the issue status 'To Do' on the cloud [To Do ----> To Do].
4. On the server, I will change the issue status category of 'To Do' ---> 'In Progress'.
5. I will perform a migration of another project and this creates a duplicate for the status, 'To Do(migrated)'.
6. Irrespective of the creation of duplicate status, the migration still fails with similar error below.

Expected Results

Not to create the duplication and synchronise with settings on the server.

Actual Results

Workaround

Not known