Your first stop for learning how to get started with Jira Service Management.
For any team in , queues are critical for the service project as your agents use queues to categorize, prioritize, and take actions on requests. Queues act as filters for requests. They can be set to show specific requests based on their type, status or something else, using a JQL statement.
As teams grow, it is important for you, as a project admin to consider how you set up your queues so the team can manage requests efficiently, which includes managing load times but also mental load for your team.
Prioritize work using queue sections
Queues are arranged into 3 sections: Starred, Team priority, and Other in the project’s sidebar. Queues under Starred and Team priority will refresh and update their issue counts regularly. Queues under Other do not refresh, and are collapsed by default.
For users on Enterprise plans, queues are divided into Starred, Priority group, and All queues in your project’s sidebar. Queues under Starred and Priority group refresh and update their issue counts regularly. Queues under All queues do not refresh, and are collapsed by default.
Any given queue will only refresh its count up until 999 issues at which point it will display 999+. For the best experience, agents should only see and refresh the queues that are relevant to them.
Limit the number of queues in team priority
It can be tempting to put all your queues into Team priority. Data shows that on average an agent views no more than 3 queues each week. With all the queues under this section, every agent has to take on a lot of additional mental load, extra refreshing and scrolling.
Start by moving all queues to the Other section.
Encourage team members to Star the queues most relevant to them. Learn more about starring queues.
Consider which queues are critical to the success of your team (e.g. high priority, expiring SLA, and/or high impact). Gradually move these queues into Team priority.
Create priority groups (Jira Service Management Enterprise plans only)
Consider which queues are critical to the success of your individual teams (for example, high priority, expiring SLA, and/or high impact). Organizing these queues to their respective priority group helps your agents work on the right set of queues that are most important to their own team. Agents can freely switch between priority groups to change focuses. Find out how to prioritize queues by groups.
Encourage agents to Star the queues that are most relevant to themselves. Read more about starring queues.
Avoid queues that attempt to return too many issues
These queues have often been there since the beginning of your project. They help small teams visualize and design a structure that helps them grow. But as the number of issues in the project and site grow, these queues become a performance burden, especially when they are included in the refreshing sections.
Delete or move to Other any queues that attempt to return all issues.
Show only recent issues, e.g. use updateDate < 14d in your JQL.
Use filters for viewing and managing large issue sets. Learn more about advanced searching in Jira Cloud.
Reconfigure queues that use complex JQL clauses
All queues utilise Jira Query Language (JQL), which is Atlassian’s proprietary language for querying issues. Similar to other database queries. Often it is better to have multiple simple queues than one complex one. Learn more about optimising JQL.
Avoid queues that analyse across multiple custom fields, complex functions, and/or labels.
JQL clauses provided by Marketplace apps installed on your site can sometimes be problematic. Reduce their use if a queue is underperforming.
Update the queues that search text fields for keywords
It is possible to create queues that will perform full-text searches across issues. These queues perform on-the-fly categorization, and might suggest room for improvement in your request structure. For example, you might be trying to extract “summary ~ ‘fault’” or “description ~ ‘component name’” or the worst of all “text ~ ‘thing’”.
Use request types and hidden fields to help customer categorize issues at point of creation, then build queues based on categories.
Automation rules to categorize issues (e.g. applying components or labels) then build queues based on categories.
Use Filters or Search for finding specific issues.
Build dynamic queues that work for individuals
Queues in the Team priority section are sometimes not for everyone. When faced with all the noise of a busy project it is not uncommon for individuals to create queues for themselves. Although this might boost their productivity, it will slow everyone else down who has to see and load a queue that is irrelevant to them.
Build dynamic queues. Utilize JQL functions like “currentUser()” to personalize queues to the individuals.
Encourage agents to star queues that are relevant to them. Learn more about starring queues.