On this page:
|
...
|
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.
...
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.
...
Adding Issue Type F to the migration may drag other projects into the migration scope.
Out-of-scope configuration isn’t migrated
| Tip |
|---|
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 to the cloud. You can see the Filters section of the Migrate Jira Software Configuration page for more details on what this transformed way entails.
...