This section overviews Queues for Jira & JSM Data Center and Cloud and includes information on migrating your app from Jira DC to Jira Cloud.
Two app versions — for both Jira Cloud and Jira Data Center — offer the same business value, design, and functionality. The only difference between the two hosting options is one feature and one integration.
The Jira Cloud version includes the Opening issue in modal feature which is not available on the Jira Data Center due to technical limitations. Additionally, the Jira Cloud version offers you an integration with the SLA Time Management app.
Before you start your migration, it’s important to understand the main differences between Jira Cloud and Jira Data Center version of the app to avoid losing the necessary data or functionalities.
| Feature | Data Center | Cloud |
|---|---|---|
| Opening issue in modal |  |
 |
| Integration between Queues for Jira & JSM and SLA Time Management | |
|
| Cross-project queues | |
|
| Creating custom queue groups | |
|
| Creating a multi-level structure of groups | |
|
| Group admin | |
|
| Notifications | |
|
| Configurable queues’ visibility | |
|
| Importing queues from other projects | |
|
| Displaying access to the application under a project | |
|
| Assigning the app’s administrator | |
|
| App’s name personalization | |
|
| Entering the app via the top navigation bar | |
|
| Creating queues | |
|
| Editing queues | |
|
| Bulk change queues | |
|
| Bulk change queues in group | |
|
| Copying existing queues | |
|
| Deleting queues | |
|
| Deleting queues in bulk | |
|
| Hiding unused queues | |
|
| Hiding unused groups | |
|
| Queue list reordering | |
|
| Searching for a queue | |
|
| Starred/Favorites | |
|
| Queue columns adjustment | |
|
| Sorting lists by any column | |
|
| Filters | |
|
| Issue counter | |
|
| Searching for an issue | |
|
| Opening issue in modal | |
|
| Opening issue in current tab | |
|
| Opening issue in new tab | |
|
| Flagging issues | |
|
| Inline assignee editing | |
|
| Audit Logs | |
|
| Due date centric & Time centric SLA support | |
|
| Integration between Queues for Jira & JSM & SLA Time Management | |
|
Before you start your migration, ensure you have two licenses, one for the Jira Data Center and one for the Jira Cloud version.
Users, groups, and columns that don’t exist in the target instance are omitted during the migration.
After checking the differences between the two hostings and ensuring that you have the necessary licenses, it’s time to start your migration to the Jira Cloud.
Currently, there is no direct migration path for app data and configurations from Jira Data Center to Jira Cloud. However, both Queues for Jira & JSM DC and Cloud offer the Export of queues to a JSON file and Import from a JSON file options.
Importing and exporting features can be used to migrate data from Jira Data Center to Jira Cloud. Follow the below steps to do that:
Before you start, log in as a user with the Jira Administrators global permission.
Queues are exported to JSON file. Now you can import queues to the Jira Cloud:
Before you start, log in as a user with the Jira Administrators global permission. What’s more, to import queues you must be a user with Jira Service agent access global permissions.
Queues exported form the Jira Data Center version are imported and visible in the Jira Cloud version. Users, groups, and columns that don’t exist in the target instance are omitted during the migration, so they need to be created again.
Currently, there is no direct migration path for app data and configurations from the Jira Data Center to the Jira Cloud. However, both versions offer the ability to export queues to a JSON file and import them into the Cloud version. Read more in the Migration process section.
Before initiating the migration, ensure you have checked the differences between the two hostings and ensured that you have the necessary licenses. You can find all the features that are available in each version on the Feature comparison section.
The app’s Cloud version allows you to open your issue in a modal, except for the two options to open the issue in the current tab ot in a new tab that are also available on the DC hosting. Read more about the opening issue in modal in the Issue preview mode chapter.
The app maintains the same design and usage across both hosting options, ensuring a consistent user experience.
To learn about the Cloud version, please refer to the Queues for Jira & JSM Cloud documentation, where you will find all necessary guidelines and information.
Migration involves exporting files from one hosting and importing them to another. So, its length depends on how quickly you go through the steps — it usually takes just a few to several minutes.
If you can’t find the answer you need in our documentation, raise a support request.
Include as much information as possible to help our support team resolve your issue faster.
