I've spent the better part of my career standing up Jira Service Management projects for clients, and I have a confession — I have a soft spot for a well-oiled queue. The clean SLA dashboards. The neatly tagged tickets. The faint hum of a workflow that actually works. It is, for a consultant, the equivalent of a color-coded sock drawer.

So when Atlassian rolled out the Service Collection announcements at Team '26 under the cheeky banner “shatter the service quo,” my first reaction was a raised eyebrow and a quiet "go on…" By the time I finished the keynote, the white paper, and Shamik Sharma's recap, my second reaction was very different: this is not a coat of AI paint on an old shed. This is a rebuild.

Here is what I am telling Avaratak's clients about what just landed.

Solution Composer: service desks in minutes, not months

If you have ever sat in a kickoff meeting for a new JSM project, you know the rhythm. Weeks of permissions matrices. Request-type debates. Queue mapping. Automation rule sketching. At least one impassioned argument about whether the field should be labeled incident or issue. It is useful work, but it is also why "we'll get the HR portal stood up next quarter" is a sentence I've heard far too many times.

Solution Composer flips that script. Admins describe the service they want in plain English — “Build me an HR onboarding portal for the Williams Racing team,” to use Atlassian's own example — and Rovo drafts the underlying workflows, request types, automations, branding, and AI agents that power it. Because it is grounded in the Teamwork Graph (Atlassian's unified data layer that maps people, services, assets, and the relationships between them), it does not start from a blank page. It reuses proven patterns from your existing Atlassian estate.

Translation for clients: configuration timelines measured in weeks are heading toward minutes. That does not make solution partners obsolete. Quite the opposite. It means our hours stop getting eaten by configuration plumbing and start getting spent where they actually matter — governance, change management, and designing service experiences people don't dread using.

Rovo Service: tier-1 deflection that earns its keep

Every "AI chatbot" I have evaluated over the last three years had the same problem. It could answer FAQs. It could not actually do anything. The moment a user needed software provisioned, access approved, or a benefits change kicked off, the bot waved a white flag and tossed the ticket over the wall to a human queue.

Rovo Service is genuinely different, and it is available now. It is an AI teammate that autonomously executes multi-step workflows — provisioning software, managing access, running HR onboarding, handling common employee requests — end to end, with humans in the loop. It taps the Teamwork Graph to understand who the requester is, what their role allows, and which approvals and downstream systems need to be orchestrated. Then it hands off to a human gracefully when judgment is required.

The phrase I keep underlining when I explain this to leadership teams is judgment is required. That is the whole game. The work that needs human nuance now actually reaches humans, instead of getting buried in a queue of password resets and birthday balloon order requests.

Incident Command Center: one place when the wheels come off

Anyone who has been on a Sev-1 bridge call knows the experience. A Slack channel, two Zoom rooms, three observability tools, a runbook in Confluence that may or may not be current, and someone in a different time zone asking "who owns this?" The Incident Command Center (coming soon) consolidates alerting, investigation, and communications into a single AI-native journey.

It pulls signals from across the Teamwork Graph — third-party observability tools like New Relic and Dynatrace, service maps from Assets, deployment data from Bitbucket, GitHub, or GitLab, even feature flags — and assembles likely root causes, blast radius, recommended actions, and predicted business impact in real time. Rovo Ops then handles the heavy post-incident lifting: drafting the PIR, and handing off to Rovo Dev to generate the work items that prevent a repeat.

The unified asset, log, and trace intelligence piece is the part that genuinely excites me. We do a lot of Assets work at Avaratak, and the long-standing pain point has always been the same — CMDB data lives in one silo, log data in another, traces in a third. When an incident hits, somebody has to mentally stitch them together at 2 a.m. Atlassian's new partnerships with Honeycomb, Lansweeper, and Coralogix mean that signal now lands inside JSM, not in yet another browser tab.

JSM grows up — and brings the right tools with it

The other quiet revolution at Team '26 is that Jira Service Management is officially becoming a full Enterprise Service Manager. Native surveys arrived with templates for HR, business, and IT — no more bolting on a third-party survey app just to capture CSAT. Workforce Optimization (currently in early access) brings real scheduling, capacity planning, and intelligent work assignment to service teams. And the platform itself is extending into HR, marketing, legal, facilities, and any other function your enterprise wants to standardize.

Pair that with Employee Live Chat in the portal — which finally lets self-service flow seamlessly into real-time human support without losing context — and you have a service experience that respects the user's time at every step. Self-service first, AI assistance next, live human when needed, in that order, without a single "let me transfer you" black hole.

What I am telling clients to do now

Three things, in order.

First, audit your current JSM estate honestly. Which projects were stood up in a rush three years ago and could be reimagined from a Solution Composer prompt instead of held together with duct tape and tribal knowledge?

Second, identify your top five repetitive tier-1 request types and ask whether Rovo Service could resolve them end-to-end. That is where ROI shows up fastest, and where credibility for the broader AI program gets earned.

Third, if you operate incident response at any meaningful scale — or if you run an Assets practice that has been waiting for the day asset, log, and trace data finally play nicely together — start planning now for how the Incident Command Center reshapes your runbook strategy. The teams that get ahead of this will look like wizards in twelve months.

The service desk of 2026 does not look like the one we built in 2019, and the gap is only going to widen. The good news is that the platform is finally doing the heavy lifting, which means humans get back to the work humans were always meant to do. That is a future worth advising on — and one we at Avaratak Consulting are genuinely excited to help our clients build.