nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

How to Organize IT Sub-Team Queues in a Single Service Desk Project

REHAB HelpDesk

We're currently building out a single Jira Service Desk project as a ticketing system. In our IT department we have 3 sub-teams with 5 techs in each sub-team; Helpdesk team, Server team, and Application team.

All customer tickets will first be picked up by the Helpdesk to investigate. If the helpdesk needs to escalate the ticket to Server team, the department would like it set up so the ticket is escalated to some sort of Server team queue/container that anyn one of the 5 techs in the server team can grab the ticket and assign it to themselves.

What is the best way to set this up in Jira Service Desk? Thanks!

Accepted answers

Jack Brickey

based on what you have shared here is what i suggest...

Define Components for your sub-teams: Helpdesk, Server, Application

Create four queues based upon components: Triage, Helpdesk, Server, Application

All new issues come into the initial Triage queue
Helpdesk team triages and sets the component to align with the sub-team
Sub-teams deal with their specific queues

Alternative to components: define Request Types that align with each team and define queues to align with Request types. For example you can create groups on the portal: Helpdesk, Server, Application w/ various request types under the group.

there are other ways too.

All comments

Gaston Valente_dzz4x1

Hi,

I really depends on the way you're working and the licensing.

You can solve everything with only one project and all users being agents as you said or maybe you can setup a SD project and internal projects for every sub-team

When a ticket needs scalation an agent creates a linked issue in an internal project and the sync between the two is done with automation rules.

Here you have a trade-off, between simplicity (one project with all tickets) and a more organized setup, but which one is better depends on the number of issues being created, the number of issues being escalated and a lot of factors.

hope it helps you

Jack Brickey

based on what you have shared here is what i suggest...

Define Components for your sub-teams: Helpdesk, Server, Application

Create four queues based upon components: Triage, Helpdesk, Server, Application

All new issues come into the initial Triage queue
Helpdesk team triages and sets the component to align with the sub-team
Sub-teams deal with their specific queues

there are other ways too.

REHAB HelpDesk

We want to keep everything in one project. Thanks for the info.

REHAB HelpDesk

Thanks for the info. Components sounds like the easiest way to go.

Gaston Valente_dzz4x1

great!

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

jira-service-desk