Assets is now available to all Jira users: What’s next for AssetIT

Big news for Jira teams: Atlassian Assets is no longer just for service desks. Since September 1, 2026, Assets is included with Jira Standard, Premium and Enterprise plans, starting with single-site organizations.

That means many more teams can now keep a shared record of their laptops, servers, software and other important things right inside Jira. It’s a real step forward, and we think it’s great for the whole ecosystem.

It also raises a fair question. If Assets is built in, where does an app like AssetIT fit? Here’s the short answer:

Atlassian Assets helps you model and connect assets. AssetIT helps you manage them throughout their lifecycle.

Let’s unpack what changed, what it means for you, and what’s next for AssetIT.

What changed with Atlassian Assets in 2026

It’s been a busy year for Assets. Here are the changes that matter most.

Assets became its own app

Earlier this year, Assets moved out of Jira Service Management and became a standalone app in Atlassian Administration. Admins now manage its roles, billing and data residency there, and existing permissions carried over automatically.

Why it matters: Assets is no longer “a service desk feature.” Atlassian now treats it as a shared layer of data for the whole platform.

Assets reached more plans

First, Assets was added to Service Collection Standard, with 5,000 objects included. Then, on September 1, 2026, it became generally available in Jira and Teamwork Collection.

Here’s how many objects each plan includes. An “object” is one record in Assets, like a single laptop or a software license.

A few details worth knowing:

• Single-site organizations get access first. Multi-site organizations follow next calendar year.
• Allowances add up across your subscriptions. For example, Service Collection Premium plus Jira Standard gives you 51,000 objects.
• Extra objects cost $0.02 per object per month at list price.
• Billing for extra usage starts on December 3, 2026, for monthly customers and for anyone who started using Assets after September 1.
• If you reach your limit and extra usage is off, creating new objects pauses. Your existing data stays viewable and editable.

Assets got smarter and more connected

Assets data now feeds into the Teamwork Graph, which links your work across Atlassian apps. You can also ask Rovo, Atlassian’s AI assistant, questions about your assets in plain language.

On top of that, Assets fields in Jira can now hold up to 200 objects instead of 20.

What Atlassian Assets does best: model and connect

Think of Atlassian Assets as a flexible map of everything your organization depends on. You decide what to track, how it’s structured, and how things relate to each other.

In plain terms, Assets helps you:

• Model your world. You create your own structure (Atlassian calls these schemas and object types). A laptop, a server, an application, a business service: each can have its own fields.
• Connect the dots. You link objects together, so you can see which service runs on which server, or which team owns which application.
• Find things fast. With Rovo, you can search your assets by asking a question in plain language, and Rovo turns it into a query for you.
• Bring data in. On Service Collection Premium and Enterprise, Data Manager pulls records from sources like Microsoft Intune, Lansweeper and Flexera into Assets.

That’s a powerful foundation. Knowing what you have and how it’s connected is step one for any team.

But a map isn’t a process. Once you know a laptop exists, someone still has to buy it, hand it out, take it back, fix it, renew its software and eventually retire it. That’s where lifecycle management comes in.

Where AssetIT comes in: managing the whole lifecycle

Every asset has a life story. It’s bought, handed to someone, used, maintained, maybe lent out, and one day retired. AssetIT is built to manage that story, from procurement to disposal, right inside Jira (AssetIT on the Atlassian Marketplace).

Here’s how AssetIT supports each stage:

1. Bring it in. Keep hardware, accessories, consumables and software in one inventory. Import devices from Microsoft Intune and Jamf with the Asset Importer add-on.
2. Assign it. Check assets out to people and check them back in, with approvals and custody checks so you always know who has what.
3. Share it. Book, reserve and lend assets without double bookings.
4. Onboard and offboard. Automate getting equipment to new starters and back from people who leave.
5. Keep it running. Track maintenance, and update asset details straight from a Jira work item.
6. Stay compliant. Track software licenses, renewals and compliance.
7. Find it fast. Generate and scan QR codes to locate and update assets on the spot.
8. Report on it. Build reports and dashboards, and export them to CSV or PDF.
9. Retire it. Close out the asset’s life when it’s time for disposal.

The key difference is focus. Atlassian Assets gives you a flexible structure that you shape yourself. AssetIT gives you the day-to-day workflows that move an asset through its life, ready to use.

AssetIT is also proven in real teams. Today it has more than 1,500 installs and a 4.7/5 rating from 71 reviews on the Atlassian Marketplace, and it runs on both Jira Cloud and Jira Data Center.

Model, connect, manage: how the pieces fit

You don’t have to choose one way of thinking. The two ideas answer different questions.

A few simple ways to decide what you need:

• You mainly need a map of services, systems, and how they depend on each other. Atlassian Assets is a strong fit.
• You mainly need to run the asset lifecycle, like handing out laptops, tracking who has what, booking equipment, or renewing licenses. That’s what AssetIT is made for.
• You need both. Many teams will. Use each for what it does best.

One practical thing to keep in mind: Atlassian Assets counts every stored object toward your allowance, and extra objects are billed from December 3, 2026. Lifecycle tracking tends to grow over time, because you keep records of retired and disposed assets too. AssetIT’s documentation states there are no limits on the number of assets you track.

What’s next for AssetIT

Atlassian is clearly paying attention to the lifecycle too. At Team ’26 Europe in October, it announced Hardware Asset Management, a new module for Jira Service Management that covers issuing and retiring devices and flags things like warranty expirations. No release date has been shared yet.

We see that as a sign that lifecycle management matters. And it’s exactly where we’ve been focused. AssetIT’s lifecycle workflows are available today, for Jira and Jira Service Management, on Cloud and Data Center.

Already using Atlassian Assets? Bring your data with you

If you’ve already started in Atlassian Assets, you don’t have to start over. AssetIT can import your data from Assets today, so your team can switch to AssetIT and keep the records you’ve already built.

Here’s where we’re heading next.

Going deeper into the lifecycle

We’re adding more depth to each stage of an asset’s life. Our goal is simple: give you more control from the day an asset arrives to the day it’s retired, without building the process yourself.

We’ll share more details as each update lands. Keep an eye on our updates for the latest.

The bottom line

Assets coming to every Jira plan is good news. More teams will start thinking seriously about the things they own and depend on.

Here’s what to remember:

• Atlassian Assets is now included in Jira Standard, Premium and Enterprise, with 1,000 objects to start.
• It’s excellent for modeling your assets and connecting them to your services and work.
• Managing assets through their life (assigning, lending, maintaining, renewing, and retiring) is a different job, and that’s where AssetIT shines.

Want to see the lifecycle side in action? Try AssetIT free on the Atlassian Marketplace or get in touch with our team for a demo.