What is Assets?
Assets has moved to platform! That means it is now accessible from any Jira app directly through the app switcher.
The information about anything your team cares about is usually scattered across spreadsheets, separate tools, and people's heads.
When a new employee starts, the people team holds their details, procurement holds the vendor and the contract for the software they need, and facilities holds the location they'll work from. Each team can answer its own part of the question, but no one can see the whole picture, so simple requests stall while people chase the missing pieces.
What Assets is
Assets helps teams track anything that matters to their business - services, employees, vendors, contracts, locations, and equipment - and connect it to the work they already do.
Everything you track is stored as an object. Each object has attributes that describe it, such as an owner, a status, or a renewal date, and references that link it to other objects, such as the vendor that supplies a service or the person responsible for a contract. Those links are what turn separate lists into a picture your team can follow.
Because your objects are connected to the work you already do, your team's important data stays in one place instead of being copied between tools and slowly going out of date. In short, Assets gives your team one place to track, connect, and act on the information behind its work.
What teams can track
Teams use Assets to track services, employees, vendors, contracts, locations, facilities, and IT equipment - anything your organization relies on to get work done.
Services - the things your organization provides or depends on, and the teams that own them.
Employees and people - who works where, what they're responsible for, and what they've been given.
Vendors - the suppliers behind your services, and who owns each relationship.
Contracts - agreements, their owners, and the dates that matter.
Locations and facilities - sites, offices, floors, and the resources attached to them.
IT equipment and hardware - laptops, phones, and other equipment, and the people they're assigned to.
These are common examples rather than a fixed list. Because you define the objects and attributes you need, teams outside IT use Assets for the information their own work depends on.
Jira Service Management only: if your team uses Jira Service Management, you can also connect objects to requests, incidents, problems, and changes, so agents can see what's affected before they act.
Get started
To start using Assets, work through these articles in order:
Assets glossary to learn the terms used across the Assets articles.
What can you do with Assets? to see the everyday jobs teams use it for.
Get started with Assets to set up your first objects.
Was this helpful?