Manage out-of-scope dependencies
Manage dependencies that are outside the migration scope
The Cloud Migration Tool aims to migrate the configuration originally added by a Jira administrator to the migration scope. However, projects and boards have dependencies on other Jira configuration elements. A project or board will function properly on the cloud when the configuration elements it is associated with are migrated too.
For that reason, when you’re migrating a project or board from Jira Server/Data Center to Jira Cloud, the Cloud Migration Tool migrates these necessary dependent configurations to the cloud beforehand.
For example, when you’re migrating a project, the Cloud Migration Tool will also move the issue types, custom fields, and workflows associated with the project. If the dependent configuration elements already exist in Jira Cloud, the migrated project will be associated with them during the migration.
However, not all dependent elements of the configuration in the migration scope can be moved to the cloud.
What are out-of-scope dependencies and configurations
In some specific cases, the projects or boards in the migration have dependencies on configuration elements outside the migration scope, and the Cloud Migration Tool won’t move them to the Jira Cloud site. We call them out-of-scope dependencies and, respectively, the configuration itself out-of-scope configuration.
In the following example, we’re illustrating what an additional dependency may be like. You can see that adding Project A to the migration scope also adds Issue Type Scheme B and Issue Type C, but selecting Board D doesn't include Issue Type F although Card Color E has a dependency on it.
Adding Issue Type F to the migration may drag other projects into the migration scope.
Out-of-scope configuration isn’t migrated
The out-of-scope dependency logic in the Cloud Migration Tool is built to prevent significant spikes in the migration scope.
Out-of-scope dependencies are detected on the analysis phase of a migration, and the out-of-scope configuration elements aren’t migrated to the cloud.
This way, we avoid including projects in the scope that the Jira admin hadn’t intended to migrate in the first place.
Let’s assume a board in the migration scope uses a filter that references three out-of-scope projects in its JQL query. The Cloud Migration Tool won’t move these projects, and the filter will be migrated to the cloud in a transformed way. You can see the Filters section of the Migrate Jira Software Configuration page for more details on what this transformed way entails.
During the analysis of the migration scope, the Cloud Migration Tool detects out-of-scope dependencies of the migrated configuration elements and shows you the following warning in these cases:
“Dependency on a missing <ELEMENT> “<NAME>”. The <ELEMENT> won’t be migrated.”.
This warning means that the migrated configuration element depends on an element that is out-of-scope, and such an element can’t be found on the Jira Cloud site.
The migration can continue, but the missing element won’t be migrated.
You won't see the warning when the out-of-scope configuration already exists on the Jira Cloud site. In this case, the Cloud Migration Tool will automatically associate the migrated configuration element with the dependent configuration on the cloud.