Migration matrix
From | To | Result |
|---|---|---|
Server | Cloud | Not available - work in progress (through migration tool) |
Server | Server | Instant (same app, different license) |
Data Center | Cloud | Not available - work in progress (through migration tool) |
Data Center | Server | Instant (same app, different license) |
Cloud | Server | Won’t be available |
Cloud | Data Center | Won’t be available |
Main differences
Feature | Server (& Data Center) | Cloud |
|---|---|---|
Multiple triggers for scheduled issue | Yes | No (in consideration) |
Workflow triggers | Yes | No |
Export/Import | Yes | No |
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) |
Scheduling existing Jira issue with its subtasks | Yes | No |
Moving SI between projects | Yes | No |
App access granted on | Global level | Project level |
Detailed statistics | Yes | No |
Custom JQLs for created issues | Yes | No |
Fails/incomplete notifications | No | Yes |
SI panel on created Jira issue | Yes | No |
Upcoming execution view | Yes | No |
Upcoming executions export | Yes | No |
From Server to Cloud
This is probably the most important migration for all of our customers.
We