(Migrated) in Issue configuration after migrating Jira Server to Jira Cloud

Question

Default Issue configurations will be flagged as (migrated) in the cloud instance.

For Ex: Initially, my instance has default configurations

Default Issue Type Scheme

Default Issue Type Screen Scheme

Default screen Scheme

Default field configuration

After Migration my instance has configurations

Default Issue Type Scheme

Default Issue Type Scheme (Migrated)

Default Issue Type Screen Scheme

Default Issue Type Screen Scheme (Migrated)

Default screen Scheme

Default screen Scheme (Migrated)

Default field configuration

Default field configuration (Migrated)

Question1: Why these flagges are comming after migration?

Question2: why we are unable to delete default configurations?

Regards -

Ganesh

RMahajan-Empyra · Answer

Hi @Ganesh Kondeti ,

You can manually edit the scheme name to remove the "(Migrated)" suffix.

Regards,
RMahajan

Ganesh Kondeti · Answer

Hi @RMahajan-Empyra

In Server i have default configurations associated with different projects, so after migration, I need same names (Default configuration names) in the cloud. Instead of that I have default names along with "(Migrated)".

So in this case, how can i get same Configuration names as in the server.

any possibulitys have that same names in cloud?

RMahajan-Empyra · Answer

Hi @Ganesh Kondeti ,

In Jira Cloud, when performing a migration, especially from Jira Server or Data Center to Jira Cloud, you might notice the addition of the "(Migrated)" suffix to certain default configurations. This is a result of the migration process and serves as a way to differentiate between configurations present in the original server instance and those created or modified during the migration to the cloud.

Question 1: Why these Flagges are coming after migration?

The addition of "(Migrated)" to default configurations aims to prevent conflicts or potential issues with existing configurations in the cloud. It helps preserve the original configurations and provides clarity on what has been migrated.

Question 2: why we are unable to delete default configurations?

In Jira Cloud, some default configurations are essential to the system and cannot be deleted by design. This is necessary for maintaining stability and functionality within the Jira Cloud instance. Default configurations such as Issue Type Scheme, Issue Type Screen Scheme, Screen Scheme, and Field Configuration are fundamental components of the Jira system.

For instance, "Default Issue Type Scheme (Migrated)" may have been created to avoid conflicts with any existing schemes in the cloud instance.

Hope it will help!

Regards,
RMahajan