In the Atlassian ecosystem, there are tools that emerge discreetly... and others that mature to become essential. Assets belongs to the second category.
what started as a solution for managing assets within Jira Service Management has turned into a genuine reference platform to map, control and connect key information from any organisation. And now, Atlassian makes it clear: Assets is becoming independent.
New home, new possibilities
There is no longer a need to "search within JSM" to work with Assets. From now on, Assets has its own dedicated space.Like Jira or Confluence have. A direct access, straightforward, that allows users with agent roles to explore, manage and build without friction.
But this is not just about visibility. its about identity.
Assets ceases to be a function within another tool to become a complete experience, coherent, customisable and designed to scale.
🧱 What does this mean for your team?
Assets is consolidating as the relational database of your Atlassian ecosystemIt is the place where you can:
- Map physical or digital assets.
- Link those assets to tasks, equipment, services or contracts.
- Integrating that structure with workflows, automations, or analytical dashboards.
A laptop? A licence? A room? A database?
Everything fits in Assets. But the best thing is not just to record… it is to relate.
Because when objects do not exist in isolation, but are connected to decisions, tickets, equipment and documentation, You are beginning to have a truly operational vision..
🧠 What this change tells us (even if it doesn't say so)
Since Quabu, we read between the lines: this is one more step towards a interconnected work platform, where the data is understood among themselves, and there is no need to leave Atlassian to map it all out.
Assets is increasingly resembling a structural motor that can feed:
- Intelligent automation (for example, what to do if an asset becomes obsolete?)
- Business reports with real context.
- Audit and compliance processes with true traceability.
- And soon, AI flows with Rovo!
🔍 Where is the opportunity?
For many companies, Assets remains underutilised. But with this shift in focus, Atlassian is positioning it as the place where order is born: A space where IT, HR, logistics or security can speak the same language of objects and relationships.
If you ever wanted to do an inventory, a real CMDB, or simply stop relying on spreadsheets now is the time.
And if you were already using Assets, now is a good time to rethink your frameworks, modernising the structure or exploring integrations with Confluence and Jira Software beyond the usual.
🛠️ And in practice?
Since Quabu, we have been helping clients to:
- Transforming ancient structures into living schemes.
- Automate maintenance, renewals or deliveries.
- Convert assets into 'triggers' for automated actions.
- Use Assets as the backend for IT and business workflows.
The new interface is just the tip of the iceberg. The real change is cultural: Assets goes from being 'a database' to becoming the internal graph of your organisation..
🏁 Conclusion
The fact that Assets has its "new home" is not just a change of interface. It is a statement of intent: Atlassian bets on ensuring that your assets are no longer disconnected from real work..
And that, for us, is excellent news.
Would you like to explore how Assets can help you organise your world (digital or physical)?
At Quabu, we accompany you from the idea to the deployment.