Release notes 3.1.2

JCMA Migration Support

We're excited to announce support for Jira Cloud Migration Assistant (JCMA), enabling seamless migration of your Smart Issue Templates data from Jira Data Center to Jira Cloud.

What's New

JCMA Integration

Export your Smart Issue Templates configuration directly through Atlassian's official Cloud Migration Assistant. The plugin registers as a Forge migration listener that automatically participates in JCMA migrations.

Scope Migration

• Export all your scopes with their complete configuration

• Project assignments preserved (via project ID mapping)

• Issue type mappings transferred

• Group permissions maintained

• User permissions maintained

• Owner information migrated (includes display name, email, and admin status)

• GLOBAL scopes are excluded from migration (Cloud handles these differently)

Pre-Migration Checks

• Project-aware scope validation (checks if scopes exist for selected projects)

• Success status indicates data is available for migration

• Detailed counts logged server-side for troubleshooting (not visible in JCMA UI)

Large Dataset Support

• Optimized for migrations of any size

• Handles 10,000+ scopes efficiently

• Automatic chunking for reliable processing (1,000 scopes per chunk)

Re-run Safe

• Running a migration again? Data is identified by source IDs

• Existing data can be updated, not duplicated

• Safe to retry after interruptions

Supported Entities

Migration Features

• Progress Tracking: Monitor migration status in real-time through JCMA logs

• Cancellation Support: Cancel a migration at any time; already-migrated data remains intact

• Error Handling: Detailed logs help identify and resolve any issues

Scope Data Exported

Each scope includes:

• Name and ID

• Owner information (display name, email, admin status, user key, username)

• Global flags (project, issue type, group, user)

• Project IDs

• Issue type IDs

• Group names

• Usernames

Known Limitations

• Templates and Hierarchies migration not yet available (coming in a future release)

• GLOBAL scopes are excluded from migration

• Owner user must exist in source Jira instance for full details to be exported

• Pre-migration checks show success/no-data status only; entity counts are not visible in the JCMA UI (logged server-side for debugging)

Feedback

We'd love to hear about your migration experience. Please report any issues or suggestions through your usual support channels.