This chapter provides information on how to configure Queues for Jira & JSM.
Before you start, log in as a user with the Administer Jira global permission.
Deviniti’s Rovo Assistant provides access to a virtual assistant that helps you with configuration, installation, and troubleshooting, enabling quicker and faster navigation through documentation.
See Deviniti’s Rovo Assistant documentation or find it on the Atlassian Marketplace for more information.
You need to access the Configuration page to manage global settings for the Queues for Jira & JSM.
To do that, navigate to Jira sidebar > Apps > Three dots > Manage apps > Deviniti Queues and open the Configuration page.
On the Configuration page and in this chapter, the app is referred to as Deviniti Queues instead of Queues for Jira & JSM for clarity within the Jira interface.
There are five tabs on the Configuration page:
Save and Discard buttons work globally across tabs (Except Slack notifications tab, where they aren’t displayed), allowing you to switch between tabs while retaining or canceling any changes made in other views.
Below is a live demo presenting the Configuration page. Additionally, you can review each tab in more detail by following the sections described in this chapter.
The Permissions tab allows you to configure user permissions globally for all queues. By default, Deviniti Queues are managed by site administrators. However, this permission can be delegated to other groups of users.
Select group or groups of users who can administer Deviniti Queues in addition to users with Administer Jira global permission so that the queues configuration panel is visible for the chosen groups.
Jira Administrator will see all queues despite limited visibility.
In the Visible to field when configuring a queue, the users are referred to as:
The Settings tab allows you to configure the Users’ preferences management and Editing assignee features.
In this section, you can adjust the view of your users’ queues by selecting the features you want to make available to them.
Use the toggles to customize the settings of the following features:
Users can adjust their personal preferences individually, overriding the preferences set here.
For more information on Personal preferences and available features, refer to this chapter.
In the Editing assignee section, you can decide whether users can assign issues to Jira users directly from the view of their queue. When the toggle is turned off, all app users won’t be able to do that.
To learn more about editing assignees, refer to the following chapter.
This tab lets you choose how users access Deviniti Queues from the Jira interface.
In this section, you can choose the projects where the Deviniti Queues UI link will be visible in the project’s menu. You can either select projects from the list or choose:
The Home container toggle allows you to enable or disable the Deviniti Queues UI link in Jira sidebar > Apps (the Apps section of the Jira main navigation).
This tab allows you to choose whether we can collect additional data.
To suit your needs better, we need to understand where in Deviniti Queues we should focus our development efforts.
Your agreement allows us to collect numerical, anonymized data explaining how your users interact with Deviniti Queues, so we can let them enjoy their work even more by improving the product’s features and your users’ productivity.
Please see our EULA and Privacy Policy for details.
To enable Data collection, turn on the toggle.
This tab enables the configuration of the Slack notifications feature (available in Queues for Jira & JSM version 5.0.0 and later), which is necessary to integrate Queues for Jira & JSM with the Slack app. The feature allows you to connect an organization’s Slack channels to specific queues. Users added to these channels will receive instant notifications in the Slack app whenever new issues are added to the queues.
Read more about this feature in the Slack notifications chapter.
The Forge migration tab informs you about the status of the automatic migration of Queues for Jira & JSM data to the Atlassian Forge platform. This tab was introduced as part of the app’s transition to Forge, Atlassian’s cloud app platform, which improves security, reliability, and platform compliance.
The migration is handled automatically by the app and does not require any action from administrators. Once the migration is scheduled, it starts automatically within 24 hours.
During the migration, the app operates in read-only mode, which means users cannot create, edit, or delete items. The process typically takes only a few minutes. If the migration fails, the system automatically schedules another attempt within 24 hours. In the meantime, the app continues to work normally.
After the migration is successfully completed, the app becomes fully integrated with the Forge platform and ready to use.
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.
Back to App page