How to Use Jira Service Management as Your Internal IT Help Desk

An internal help desk built on Jira Service Management gives every IT request a home: employees raise tickets from a portal or by email, each one lands in a queue with an owner, and answers stop living in scattered chat threads. The setup runs in six short steps:

• Create a service space from the IT service management template and trim its request types
• Add your IT team as agents and open the portal to every employee
• Connect an email address and build queues that match how you triage

Verified against Jira Service Management Cloud on 2026-08-19.

Prerequisites

• A Jira admin account: only Jira admins can create spaces
• Jira Service Management on your Jira Cloud site: agents need licenses, while employees raising requests do not
• A note on names: current Jira Cloud calls projects "spaces" and issues "work items." The steps below use the labels you will see on screen today.

Step 1: Create the Service Space

1. In Jira's sidebar, select + next to Spaces.
2. Select the Service management category, then choose the IT service management template and select Use template. It ships with request workflows, automation flows, and service-level agreements ready to configure. Pick the company-managed space type if you are offered a choice, since the agent and email steps below assume it.
3. On the Create space screen, enter a name such as IT Help Desk, keep or edit the generated space key, and select the type of team that will manage incoming requests.
4. Select Create space.

Step 2: Trim Request Types to What IT Actually Handles

1. On the welcome screen gallery, preview each default request type to see the form employees will fill out in the portal.
2. Keep a small starter set, such as getting help with a tool, reporting something not working, and requesting access or hardware. Select Add for each one you want and Remove for the rest, then select Continue to space.
3. To adjust later, go to Space settings → Request types and edit the fields there.

A short request list is what keeps the portal usable: employees pick the right form when there are five choices, and guess when there are twenty.

Step 3: Add Your IT Team as Agents

1. In your service space, go to Invite team.
2. Enter each agent's email address and select Invite.

Invited agents land in the Service Space Team role and receive an email link to the space. If someone is brand new to your Jira site, an organization admin needs to add them.

Step 4: Open the Portal to Every Employee

1. Go to Space settings → Access → Customer permissions.
2. Under Channel access, select Open.

For an internal help desk, open access is the setting you want: every employee can raise requests without waiting for an invite, and anyone who emails the space becomes a customer automatically. If your site policy requires a restricted portal instead, add people from the Customers tab with Add customers, separating addresses with commas to bulk-add a whole team.

Step 5: Connect the Email Channel

1. Your space comes with a pre-configured Atlassian cloud email address that turns incoming mail into work items immediately.
2. For a friendlier address, select Channels & self service → Email, then Create Atlassian email, and enter a prefix: support becomes support@companyname.atlassian.net. Pick the request type incoming mail should create, then select Create.
3. To use an address on your own domain, select Add external email and connect it with Continue with Google or Continue with Microsoft.

The request type that receives email must have both Summary and Description fields visible, and every other visible field must be optional. A space can hold up to 10 connected addresses, which is plenty of room for a separate onboarding or security alias later.

Step 6: Build Queues That Match Your Triage

1. Next to Queues in your space, select More actions (•••), then Queue settings.
2. Select Create new queue and name it.
3. In the Filter by section, select the types and statuses the queue should show, or select Advanced to write a JQL statement.
4. Set the sort under Order by, then select Create.

Starter queues that serve most SMB IT teams:

• Everything unassigned, so nothing sits without an owner
• Access and hardware requests, which follow approval paths
• Waiting on employee, so agents chase replies instead of rediscovering them

This structure works the same for a 5-person startup and a 120-person company. Configure it for scale from day one, and if your requests currently live in a shared inbox, it is not too late to move them.

Verify

• Raise a test request from the portal and confirm it appears in your new queue.
• Send an email to the space's address from a personal account and confirm it arrives as a work item.
• Have an agent assign the test work item to themselves and reply, and confirm the requester receives the response.

Troubleshooting

Emails arrive but never become work items: the receiving request type is hiding Summary or Description, or has another required visible field. Fix the field visibility in Space settings → Request types.

Employees cannot see the portal: Channel access is still restricted. Set it to Open under Space settings → Access → Customer permissions, or add the missing people from the Customers tab.

A new agent cannot pick up tickets: they were invited to the space but never added to the Jira site. Only organization admins can add brand-new agents, so have yours complete the invite.

Would you rather have the help desk stood up for you, with request types, queues, and service targets tuned to your stack? ScaleIt sets up and runs Jira Service Management for startups and SMBs as part of managed IT. Book a free call and we will map the setup to your team.

Verified against Jira Service Management Cloud (Create space, Invite team, Customer permissions, Channels & self service → Email, and Queue settings flows) on 2026-08-19. Vendor docs: support.atlassian.com/jira-service-management-cloud.