Smart Issue Templates for Jira Cloud
Smart Issue Templates for Jira Cloud
Breadcrumbs

Import Scopes to Cloud

Import the scopes-export-YYYY-MM-DD.json file created by the Data Center Manual migration export. Import scopes first: templates and hierarchies refer to them.

This is part of the Manual migration (Alternative). To create the file, see Manual migration (Alternative) in the Data Center documentation.

How to Import Scopes

  1. Open Smart Issue Templates and select Scopes in the top menu

  2. On Manage scopes, open the More actions (...) menu and select Import

  3. In Import Scopes, choose the scopes-export-YYYY-MM-DD.json file

    out_scopes_file.png

  1. Review the file. The dialog shows Scopes in file and Issues found, with a table of issues (Scope, Field, Issue, Severity)

    out_scopes_preview.png

  1. Click Import. When there are issues, the button is Import anyway: Importing anyway will skip the content that cannot be resolved.

  2. Keep the dialog open until it finishes, read the result, then click Close

    out_scopes_result.png

A file can hold at most 1,000 scopes. A larger file stops with This file holds N scopes. The most that can be imported at once is 1000. Contact support if your export is larger.

How Scopes Are Matched

Scope property

How it is matched

If it cannot be matched

Name

Copied as it is

A scope with no name is skipped

Projects

By name, by key, by "Name (KEY)", or by name ignoring case. All Projects stays All Projects

Left out: Project X is not on this site and will be left out.

Issue types

By name ignoring case, including Sub-task / Subtask variants. All Issue Types stays All Issue Types

Left out: Issue type X is not on this site and will be left out.

Groups

By name. All Groups stays All Groups

The scope is not imported: Group X doesn't exist. Create the group in Cloud first

Owner

The owner in a Data Center file is not matched

The user running the import becomes the owner. Reassign owners in Cloud after the import if needed

Scopes that already exist

A new scope whose name already exists on the site is skipped, and the result says how many were skipped, for example 1 scope was skipped because a scope with the same name already exists. Skipped scopes are counted as left alone.

After the import

See also Migrate from Data Center to Cloud for known limitations and frequently asked questions.