Cloud Migration Issue

[Mahdi CHIHAB]

Hi Community,

I have performed a migration Cloud-to-Cloud. Here are the outcomes : 

- From Organization A to Organization B : Full Project (full project with workflow etc...) and its issue have been migrated

- From Organization A to Organization C : For the same project, issue has not been migrated (but the project created).

From the report file, I have these kind of errors : 

Category

Referenced by project

Impacted type

Impacted name

Problem

Description

Next steps

UNSUPPORTED

Global entity (applied to all projects)

Custom field

Release[customfield_10208]

Custom field configuration

"The Release custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work."

"If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

UNSUPPORTED

Global entity (applied to all projects)

Custom field

[CHART] Time in Status[customfield_10013]

Custom field configuration

"The [CHART] Time in Status custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work."

"If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

UNSUPPORTED

Global entity (applied to all projects)

Custom field

[CHART] Date of First Response[customfield_10012]

Custom field configuration

"The [CHART] Date of First Response custom field type is not supported via migration. The configuration for this field will not be migrated and any items that reference it, such as workflow schemes and filters may no longer work."

"If you require this custom field, re-create it in your cloud site and use a csv import to update the issues post migration. Learn more : https://support.atlassian.com/jira-cloud-administration/docs/import-data-from-a-csv-file/"

WARNING

VHV

Issue

VHV-687 and VHVIT-18

Issue Link

The issue link may not work in the destination site as the project VHVIT might not have migrated.

WARNING

VHV

Issue

VHV-394 and VHVIT-188

Issue Link

The issue link may not work in the destination site as the project VHVIT might not have migrated.

WARNING

VHV

Issue

VHV-291 and VHVIT-197

Issue Link

The issue link may not work in the destination site as the project VHVIT might not have migrated.

WARNING

VHV

Issue

VHV-398 and VHVIT-198

Issue Link

The issue link may not work in the destination site as the project VHVIT might not have migrated.

UNSUPPORTED

VHV

Workflow

VHV - Default Workflow

Transition post function

"The ClearFieldValuePostFunction  is not supported via migration. The workflow will still be migrated, however, the post function on Restart transition will be skipped, which may impact the workflow in your destination."

"If you need this workflow, inspect and manually recreate it on the site. Update your workflow scheme, and ensure your project uses the correct workflow."

UNSUPPORTED

VHV

Workflow

VHV - Configuration Workflow V2

Transition post function

"The ClearFieldValuePostFunction  is not supported via migration. The workflow will still be migrated, however, the post function on Back to backlog transition will be skipped, which may impact the workflow in your destination."

"If you need this workflow, inspect and manually recreate it on the site. Update your workflow scheme, and ensure your project uses the correct workflow."

Any idea on whats happening.

Thank you very much!

[Dirk Ronsmans]

@Mahdi CHIHAB ,

Those are several issues.

1. Custom fields errors: you have certain specific fields that were added by an addon which are not supported to be migrated through the migration system. You'll have to look at the addon/app itself and see if it has a migration path or how you can mitigate those.
2. Issue link: it seems you have some links between issues and the system is unable to recreate those. This could be due to the fact that the other issue (where it is linking to) does not exist or it could be a missing link type. Keep in mind that those could be a false positive as the linked issue could be imported/migrated at a later time.
3. Post functions on workflows: It looks like you have some post functions defined on the VHV - Configuration Workflow V2 workflow. The used post function is not available on cloud or cannot be migrated so those too you'll have to look at what they are doing and if needed re-create them on the destination environment.

The migration tools can do a lot for your but you still need to validate manually what the reports tell you to do some manual post migration actions.

[Mahdi CHIHAB]

Thank you very much Dirk. I will have a look.

Actually the exact same migration is working from an Orga A to an Orga B without these errors. But it is not working from an Orga A to an Orga C

Do you have an idea on why it is not working for Orga C ?

Thanks a lot

[Dirk Ronsmans]

Well it could be that some apps that you have on A are also installed on B but not on C.

Therefor the fields and post functions could be supported on B but not (yet) on C

[Mahdi CHIHAB]

Thank you @Dirk Ronsmans 

Actually no apps are installed in B (maybe in C)

I have compared the reports of both migrations: they are exactly the same (we have the same RequiresAttention points).

So I'm a bit confused