Let me tell you about a Tuesday that changed how I think about HR.

I was sitting with the head of People at a 200-person tech company, and she was showing me her onboarding spreadsheet. Color-coded. 47 columns. Eight tabs. A legend on the side that explained what "yellow with a star" meant versus "yellow with a strikethrough." She said, with the kind of tired pride that only comes from years of holding chaos together with willpower, "This is how every new hire gets onboarded. It works. Most of the time."

I asked her what happened on the days it didn't work. She got quiet. Then she listed them: laptops that arrived three days after start dates, badges that didn't open the right doors, payroll setups that got missed because someone was on PTO when the email came in, new hires sitting in lobbies wondering if they had the wrong building. Each one a small failure. Each one a story the new employee would tell about their first impression of the company.

That spreadsheet was working. And it was also, very quietly, costing the company every single hire.

I'm telling you this because the conversation that followed is the same one I've now had with HR leaders across dozens of companies. And the punchline is always the same: HR is one of the most underserved functions inside Jira Service Management, and it shouldn't be. JSM was practically built for what HR is actually trying to do.

Why HR and JSM Belong Together

Here's the framing I give every HR leader I work with.

Your job, at its core, is service delivery. Every onboarding is a service request. Every benefits question is a ticket. Every offboarding is a coordinated workflow across multiple teams. Every leave-of-absence has approvals, status updates, and SLAs that real human beings care deeply about. The mental model you've been told to use — spreadsheets, email threads, the occasional shared form — is dramatically underpowered for the work you're actually doing.

JSM was designed for service delivery. Request portals. SLAs. Approvals. Knowledge bases. Cross-team coordination. The exact muscles HR has been forced to grow inside Outlook for the last fifteen years. And the kicker: most companies already own JSM because IT is using it. The license, the platform, the integrations, the admin team — it's all sitting there, waiting for HR to walk in and use it.

The version of JSM in your head is probably smaller than the one waiting for you.

Six Ways HR Teams Are Putting JSM to Work

Let me get specific.

Onboarding orchestration. The headliner. A hiring manager submits one request — "new hire starting March 15, software engineer, San Francisco office" — and JSM cascades the work to IT (laptop, accounts, software), Facilities (desk, badge, parking), Payroll (system setup, direct deposit), and HR itself (paperwork, orientation scheduling). Each team gets the right subtask in their own queue with their own SLA. The new hire's manager sees a single dashboard of progress instead of forwarded emails. The HR team's role shifts from "coordinator-of-last-resort" to "orchestrator with visibility." When Atlassian rolled out Journeys for JSM, this exact use case is what they built it for.

Employee help desk. The catch-all. Benefits enrollment questions, payroll discrepancies, policy clarifications, "how do I update my direct deposit" — all of it lives in a clean self-service portal instead of buried in your inbox. Pair it with Confluence as the knowledge base behind the scenes, and roughly 30 to 40 percent of routine questions get deflected before they ever land on an HR pro's plate. That's not a hypothetical number. That's the average we see at clients within 90 days of going live.

Leave and absence requests. A request type with the right form fields, the right approval chain, and an automatic notification to payroll when approved. The employee gets a tracked confirmation. The manager gets a clean approval flow. HR gets an audit trail. No one is digging through a Slack thread three weeks later trying to remember what was approved.

Offboarding. The mirror image of onboarding, and arguably the higher-stakes one because security and compliance are watching. JSM coordinates account deactivation, asset return, exit interview scheduling, final pay calculations, and benefits notifications across the same teams that did the onboarding. One ticket. One audit trail. One reduced risk of the ex-employee still having Slack access two weeks later.

Internal mobility and role changes. The forgotten use case. When someone changes teams or gets promoted, there's a mini-onboarding hiding inside the change — new system access, new manager, sometimes new equipment, often new training. Most companies handle this with email and crossed fingers. JSM handles it with the same workflow muscle as net-new hires, just with different subtask templates.

Sensitive case management. The one I always recommend last because it requires real care. Investigations, accommodations, complaints — these are the cases that absolutely cannot live in shared inboxes or forwarded emails. JSM's permission model lets you create a separate, restricted-access request type where only the relevant HR business partners can see the case. Audit trail intact. Privacy preserved. Compliance happy.

What Makes the Difference Between "Tool" and "Transformation"

Two practical observations from years of doing this work.

The portal experience is the make-or-break. If your HR portal looks like a generic IT ticket form, employees will treat it like one — with the same tepid enthusiasm they reserve for filing expense reports. If it looks like a thoughtful, on-brand experience that respects what the employee is actually trying to do, they will use it eagerly. The investment is small. The behavioral shift is enormous. Custom request types, smart forms with conditional logic, and a knowledge-base sidebar make the portal feel like a service — because it is one.

Automation is your competitive advantage. Atlassian's own data shows that 65% of managerial tasks can be automated, and HR is sitting on a goldmine of repetitive coordination that JSM's automation engine handles in its sleep. Auto-routing requests to the right HRBP based on the employee's department. Auto-creating Confluence pages for new hire welcome packets. Auto-syncing with your HRIS so a new record in Workday triggers an onboarding journey in JSM. The teams that lean into this go from "firefighters" to "experience designers" within a couple of quarters.

Where Avaratak Comes In

An honest word from the trusted-advisor seat.

HR-on-JSM rollouts succeed or fail based almost entirely on the planning conversation that happens before anyone touches a configuration screen. The technical work is the easy part. The real work is mapping your actual employee experience — every touchpoint, every cross-team dependency, every "oh and we also have to remember to…" exception — and translating it into request types, workflows, and SLAs that respect how your company actually operates.

That's what we do at Avaratak Consulting. We've helped HR teams of every size go from spreadsheet-and-willpower to a service-grade employee experience inside JSM, and the results consistently land in the same neighborhood: 50 to 70 percent reduction in coordination time per hire, 30 to 40 percent ticket deflection through self-service, and the kind of audit trail that makes your compliance team smile at you in the elevator instead of catching your eye and looking away.

Three practical recommendations.

Start with onboarding, not everything. Onboarding is the highest-stakes, highest-visibility, most-broken HR workflow at almost every company. Win it first. The credibility you build there opens every other conversation.

Connect to your HRIS. Workday, BambooHR, Rippling — whichever one you use, JSM can sync. The moment a new employee record is created in your HRIS, the JSM journey can fire automatically. No more "did anyone hear we have a new hire next Monday?"

Treat the portal like a product. Your employees will use it dozens of times over their tenure. Invest in making it feel intentional. Customize the language. Add the right knowledge articles. Test the forms with real employees before you launch.

Worth Saying Out Loud

HR is some of the most consequential work happening inside any company. The stories your employees tell about how they were welcomed, supported, and respected become the stories your company is known for. Tools that make that work easier, more visible, and more consistent aren't a nice-to-have — they're a strategic asset.

Jira Service Management is one of the best-kept secrets in the HR-tech conversation, and it's hiding in plain sight inside companies that already own it. If your HR team is still running the spreadsheet-with-47-columns playbook, that's exactly the conversation we love at Avaratak Consulting. Stop by avaratak.com and bring your hardest onboarding story. Odds are very good there's a JSM workflow waiting to retire it.