Import Scopes to Cloud

To Import Scopes from 'Smart Issue Templates for Data Center' to 'Smart Issue Templates for Cloud' you need to create Scopes on the Server and Export them. You can Export one or several Scopes at one time and you'll receive a .json file with these Scopes. After that, you can start to Import these Scopes to the 'Smart Issue Templates for Cloud'.

How to Import Scopes from the Server:

1. Export Scopes from Server.

2. Open the Jira Cloud.

3. Open the 'Manage Scopes' page in the Smart Issue Templates app.

4. Click the 'Import' button.

5. Click the 'Choose JSON File' button.

6. Select the exported '.json' file from your computer (max 10 MB).

7. The system will parse and validate the file. You will see a summary showing how many valid scopes were found, along with the first few scope names for your confirmation.

8. (Optional) Select a Default Owner (Fallback) — this user will be assigned as the owner for any scopes whose original owner cannot be matched in Cloud. If you skip this step, the current user will be used as the fallback.

9. Click the 'Start Background Import' button.

10. The import will run in the background. A progress widget will appear showing the current status, and you can continue using the app while it processes.

11. Once the import completes, the Scopes list refreshes automatically with your newly imported scopes. A final summary will show the number of imported, skipped, and failed scopes.

Note: The scope import file supports a maximum of 1,000 scopes per file. If you have more than 1,000 scopes, split them into multiple JSON files and import them separately.

Supported Scope Fields

The following scope properties are carried over from Server to Cloud during import:

Note: All core scope properties are supported. You do not need to manually re-configure your scopes after import - the system handles the mapping automatically.

Intelligent Auto-Mapping

The import process automatically maps your Data Center/Server data to the corresponding Cloud equivalents. You do not need to manually re-configure each scope.

Projects are matched using multiple strategies: exact name match, project key match, "Name (KEY)" format, and a case-insensitive fallback.

Issue Types are matched by name with case-insensitive comparison. Common naming variations are handled automatically - for example, "Sub-task", "Subtask", and "sub-task" are all recognized as the same issue type.

Owners are resolved using a priority chain:

1. Email match (most reliable)

2. Display name match

3. Default Owner (the fallback user you selected during import)

4. Current user (the user performing the import)

Duplicate Detection — Scopes with names that already exist in Cloud are automatically skipped. After the import, you will see a summary of how many scopes were skipped as duplicates.

Background Import

The import runs entirely in the background after the import modal closes. You can continue working in the app while scopes are being processed.

• A progress widget appears showing real-time batch status.

• Scopes are processed in batches with automatic retry logic for transient errors.

• If multiple consecutive failures occur, the import stops to prevent cascading errors.

• When the import finishes, a summary shows the total imported count, skipped duplicates, invalid entries, and any errors encountered.

  

Note: You cannot start a new scope import while another one is still running in the background. Wait for the current import to finish before starting the next one.