Smart Issue Templates for Jira Data Center/Server
Smart Issue Templates for Jira Data Center/Server
Breadcrumbs

Cloud Migration Guide

This guide walks you through the process of migrating Smart Issue Templates data from Jira Data Center to Jira Cloud using JCMA (Jira Cloud Migration Assistant). By the end of this guide, you'll be able to start a migration, monitor its progress, and understand the results.

1. Before You Begin

Prerequisites

Requirement

Details

DC Plugin Version

3.1.3 or higher

Cloud Plugin Version

26.1.0 or higher

DC Permissions

Jira Administrator

Cloud Permissions

Organization Administrator

JCMA 1.12.46 or higher installed on your DC instance
Screenshot 2026-03-10 at 5.51.39 PM.png

What Gets Migrated

Entity

Status

Description

Scopes

✅ Supported

Scope configurations including projects, issue types, and groups

Templates - System fields

✅ Supported

Issue templates with name, description, content, project, issue type, scope, available for, summary, assignee and reporter, labels, priority, due date, components, fix/affected versions, linked issues, epic link, time tracking, environment

Templates - Custom fields

✅ Supported

Issue templates’ custom field values (e.g., select lists, user/group pickers, dates, numbers) and their mappings between Jira DC and Jira Cloud

Hierarchies

🔜 Coming soon

Template hierarchy structures

Expected Timing

Data Volume

Estimated Time

~10,000 scopes

25-30 minutes

~10,000 templates

70-90 minutes

Note: Migration time varies based on the complexity of your data, including user information, project mappings, and group configurations.

2. Running the Migration

2.1 Start Migration from Jira DC

  1. Navigate to Jira Administration > System > Migrate to cloud

  2. Create a new migration and follow the wizard

  3. In the app selection step, ensure Smart Issue Templates is selected

  4. Review the migration summary and click Run Migration

image-20260311-154739.png
image-20260311-154845.png
image-20260311-155124.png

Re-running a Migration

If you need to re-run a migration:

  • Previously migrated data will be overwritten (not duplicated)

  • This is useful if you made changes in DC after the initial migration

  • Simply start a new migration following the same steps above

2.2 Monitoring Progress

2.2.1 Plugin migration dashboard - Jira Cloud

During the migration, you can monitor progress in the Smart Issue Templates Migration dashboard:

  1. Go to Apps > Smart Issue Templates > More Actions (…) > App Settings > Migration Status in Jira Cloud

  2. You will be able to see:

Section

Description

Support Tools

Allows you to delete temporary information used for the migration, migration history and export the dashboard information

Migration Overview

Displays general information about the migration, including the Jira version, source URL, and the total number of entities to be migrated

Overall Status

Shows the current state of the migration and overall progress percentage

Entity Progress

Breaks down progress by entity (Scopes, Templates), showing records migrated, completion percentage, and status for each

Execution Timeline

Visual timeline showing when each chunk was processed, helping identify bottlenecks or gaps in progress

Chunk Timing Details

Detailed table of each chunk with processing time, records processed and status

Total amount of migrated records

Summary showing the total count of successfully migrated records for each entity
Screenshot 2026-04-15 at 4.58.26 PM.png

2.2.2 JCMA dashboard - Jira Data Center

During the migration, you can monitor progress in the JCMA dashboard:

  1. Go to Jira Administration > System > Migrate to cloud in Jira DC

  2. Find your active migration

  3. Click View details to see the logs

    image-20260428-215925.png

  4. Scroll down to find the Smart Issue Templates plugin, then click on View logs to download the migration logs as a CSV file

image-20260311-155408.png

  1. Open the CSV file, and it should look like this:

    image-20260416-173055.png
2.2.2.1 Understanding Progress Logs

Log Message

Meaning

Migration started

JCMA received the migration request

X scopes inserted (Z%)

Scopes progress update

X templates migrated (Z%)

Templates progress update

Migration completed in T

Migration finished successfully

Note: Additional logs not included in this documentation may help with technical analysis when troubleshooting migration failures.

2.2.2.2 Understanding Statuses

Status

Description

What To Do

RUNNING

Migration is actively processing data

Wait for completion. If it exceeds expected time significantly (2x or more), consider cancelling manually

COMPLETE

All data migrated successfully

Verify data in Cloud instance

TIME OUT

The migration stopped because data transfer became too slow to continue

Check the logs to identify the cause, then re-run if needed. Previously migrated data remains intact

FAILED / INCOMPLETE

Technical error or connection issue

Check error logs, verify connectivity, contact support if issue persists

2.3 Verifying Migrated Data

  1. Log in to your Jira Cloud instance

  2. Navigate to Apps > Smart Issue Templates > Scopes

  3. Verify that your scopes appear with correct configurations

    1. Spot-check a few scopes to confirm:

      1. Project assignments

      2. Issue type mappings

      3. Group permissions

      4. Owner information

  4. Verify that your templates appear with correct configurations

    1. Spot-check a few templates to confirm:

      1. Project assignments

      2. Issue type mappings

      3. System fields (name, description, summary,
        owner, reporter, assignee, issue type, etc.)

3. Troubleshooting

Common Issues

Issue

Possible Cause

Solution

Migration stuck at 0%

Plugin not properly configured

Verify plugin versions and JCMA setup

"Transfer expired" error

Migration session timed out

Start a new migration

Missing scopes after migration

Scope had invalid data

Check logs for skipped records and re-run migration

Missing templates after migration

Template had invalid data

Check logs for skipped records and re-run migration

Owner shows as "Migrated User"

Original owner not found in Cloud

Manually update owner in Cloud

Getting Help

If you encounter issues not covered here:

  1. Collect the migration logs from JCMA and migration dashboard information (Check how to do that on the 3.2.1 Plugin migration dashboard - Jira Cloud section)

  2. Note the migration ID and timestamp

  3. Contact support with this information

4. Appendix

Glossary

Term

Definition

JCMA

Jira Cloud Migration Assistant - Atlassian's tool for migrating apps from DC to Cloud

Chunk

A batch of records processed together (used for large datasets)

Transfer ID

Unique identifier for a migration session

Entity

A type of data being migrated (scopes, templates, etc.)