Migrating The Scheduler
This page will be continuously updated with migration related info.
Make sure there are no ongoing incidents before migrating: Status Page
From DC to Cloud
This is probably the most important migration path for all of our customers, to move from Jira DC to Jira Cloud. We are in process of bringing both apps closer together. We did some background work as well as internal changes in both apps, but it's a slow process.
Migration is Ready!
Since: v6.5.0 Jira Data Center
Since: v2.13.1 Jira Cloud
We are pleased to confirm that The Scheduler is ready to migrate to Jira Cloud. On Jira Data Center, ensure The Scheduler is installed at version 6.5.0 or later, and that the latest version of the Jira Cloud Migration Assistant (JCMA) is installed.
Keep in mind that you can only migrate from Jira DC versions that are compatible with JCMA. You can find all JCMA version here: Jira Cloud Migration Assistant - Version history | Atlassian Marketplace | Atlassian Marketplace
Here you can read more about the process:
Main differences
In table below we gathered some of the most important differences between The Scheduler version for Jira DC and Jira Cloud. The main focus is to show you options missing in Cloud version.
We are constantly working on bringing both apps closer together, keep in mind DC app is already mature and not everything can be easily implemented.
Feature | Data Center | Cloud |
|---|---|---|
Multiple triggers for scheduled issue | Yes | No (creates separate SI for each trigger during migration) |
Workflow triggers | Yes | No |
Export/Import | Yes | To CSV format (Export Scheduled Issues table data to CSV ) |
SI privacy/share/access | Yes Owner and administrators have access to SI | No On project level everyone with access to app have same access to SI |
Global SI page | Yes | No (in consideration) |
Number of subtasks under SI | Unlimited | 10 (can be increased on request via the following link: https://psc-software.atlassian.net/servicedesk/customer/portal/10/group/12/create/114 ) |
Scheduling existing Jira issue with its subtasks | Yes | No |
Moving SI between projects | Yes | No |
App access granted on
| Global level Managed with custom Global & Project permissions upcoming v6.4.0: Permissions | Project level Managed with custom Global & Project permissions starting: v2.8.0: Permissions |
Fails/incomplete notifications | No | Yes |
Migration matrix
In table below you can see Jira hosting type and possible migration options
From | To | Result |
|---|---|---|
Data Center | Cloud | Available (through migration tool) |
Cloud | Data Center | Won’t be available |
Migration from DC to Cloud
In table below you can see progress of implementation migration tool from DCto Cloud.
Feature | Status |
|---|---|
Migration “Scheduled Issue” with all Jira supported fields | done |
Migration “Scheduled Issue” with related triggers | done |
Subtasks migration | DONE |
Check migration progress | DONE |
Check migration logs | IN PROGRESS |