.webp)
Avaratak Blog
Assets Moves Out: Atlassian's CMDB Gets Its Own Apartment
Buried in this week’s Atlassian Cloud release notes, somewhere between a sandbox improvement and a table restyle, sit nine quiet words: “Assets is now a standalone platform app.” No keynote. No confetti cannon. Just a moving truck idling outside Jira Service Management’s house while the CMDB carries its boxes to the curb.
I’ve been waiting for this one, and I’d argue it matters considerably more than its release-note real estate suggests. Here’s what changed, why it should change how you think about your asset data, and the four things I’d check in your instance this week.
The tenant becomes an owner
For its entire cloud life, Assets has been a feature of Jira Service Management—a genuinely good one, but a tenant. It lived inside JSM’s navigation, borrowed JSM’s roles, and stayed mostly invisible to anyone without an agent seat. That arrangement is ending. Atlassian is moving Assets into Atlassian Administration as its own platform app, with dedicated roles, its own billing, and its own data residency management. Existing permissions and access migrate automatically, so the move is designed to be a non-event for your users on day one.
This wasn’t a surprise so much as a delivery. Atlassian signaled the direction at the Team ’25 Europe keynote, ran a one-time role alignment that translated legacy JSM roles into dedicated Assets roles in Atlassian Identity, and has been widening access in stages—Service Collection Standard picked up 5,000 included objects a month earlier this year, every paid Service Collection plan has the platform app today, and Atlassian has said a gradual rollout to customers outside Service Collection lands this fall. This week’s release note is the paperwork catching up with the plan.
Why a CMDB wants its own apartment
The point is not administrative tidiness. The point is the Teamwork Graph. Assets is one of the six contexts Atlassian is weaving into its graph—alongside knowledge, work, communications, code, and people—a structure we unpacked when we decoded Atlassian’s Q4 FY26 shareholder letter. Once your objects live in the graph rather than inside a single service project, they start showing up where work actually happens: platform search, Jira work items, Confluence pages, App Home, automations. Rovo Search support is in early access, with natural-language querying over your object schemas on the roadmap.
That flips the mental model. A CMDB locked inside JSM answers one question: “what is this ticket about?” An object layer woven through the platform answers a much better one: “what does this piece of work touch?” The laptop, the vendor, the contract, the service, the person—mapped, related, and reachable from wherever you happen to be standing. When we went inside Atlassian’s Service Collection, we argued that Assets was where the platform investment compounds, because the asset graph is the connective tissue between “what changed” and “what broke.” This move is that argument becoming architecture.
It also quietly widens who Assets is for. The examples that used to headline Assets demos were IT ones—laptops, licenses, servers. But the object model has always been general-purpose. Legal teams model contracts and counterparties, an approach we walked through when we showed how Assets gives a legal team a memory. Facilities teams model rooms and equipment. Procurement models vendors and renewal dates. With Assets out from behind the JSM curtain—complete with its own onboarding, a new “For you” landing page, and modernized admin settings—those teams no longer need to think of themselves as service-desk adjacent to get a proper system of record.
The supporting cast in the same release notes
Three smaller Assets items shipped alongside the headline, and together they read like a product growing up.
Backup and restore now covers Assets. Assets data in Jira Service Management is now included in the native backup and restore of your Atlassian Cloud services. If you have ever maintained a scheduled export script because your object schemas sat outside the standard backup path, you may now retire it with honors.
Asset attributes now appear in Forms. Previously, someone filling out a form saw only an object’s name and had to guess which of seven identically named laptops was theirs. Forms now list attributes alongside each object, the same way request types do. Fewer wrong picks, cleaner data downstream.
The change calendar speaks Assets. You can now attach affected services and Assets objects when creating change windows, which means change conflicts surface against the specific things they endanger rather than against vibes.
The honest caveats
Trusted-advisor hat firmly on. First, this is a phased rollout—if your Admin Hub doesn’t show Assets as its own app yet, patience beats a support ticket. Second, object allowances vary by plan, and additional objects are a purchasable line item; know your count before you invite three new departments to model their world. Third, the role alignment was a one-time automated migration, and automated migrations deserve an audit—more on that in a moment. Fourth, some of the shiniest pieces, like natural-language Rovo queries over your schemas, are still early access rather than everyday reality. And finally, this is a cloud story; Assets in Data Center carries on unchanged.
The Avaratak Take
Four moves this week, in order. First, open Atlassian Administration and audit the Assets roles the migration handed out—decide deliberately who administers, who manages schemas, and who merely consumes data, because a platform-wide object layer running on JSM-era permission assumptions is a governance question waiting to be asked. Second, check your object count against your plan’s allowance before the graph makes Assets popular; success has a way of arriving as an invoice. Third, clean your schemas now—objects that surface in platform search and Rovo answers are only as trustworthy as the data behind them, and that schema named “old-laptops-probably-v2” is about to play to a much larger audience. Fourth, verify your new backup posture by actually testing a restore, because a backup you have never restored is a rumor.
The bigger takeaway: Atlassian keeps promoting the unglamorous layer—context—to the top of the org chart, a pattern the analysts have noticed too, as we covered when Atlassian landed a Leader spot in the 2026 Gartner Magic Quadrant for ITSM. Assets going platform-wide is that strategy in miniature: intelligence can be rented by the token, context has to be owned, and Atlassian just handed your context a bigger stage.
If your Assets estate is three schemas deep and held together by the memory of one admin who is currently on vacation, this is the right month to fix that. Avaratak is an accredited Atlassian Solution Partner staffed by senior-only consultants with 5+ years in the ecosystem, and object-model design, role governance, and turning a dusty CMDB into a platform-grade data layer are squarely our kind of fun. Find us at avaratak.com, or book a discovery call and bring your messiest schema.