Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
Get started with Assets in Jira Service Management
As of 16 October 2024, usage limits will apply to Assets and the virtual service agent in Jira Service Management. See our blog article for more details.
Assets in Jira Service Management is a Premium and Enterprise only feature. Tell me more about Assets.
Special permissions apply to users when viewing or editing Assets objects custom fields:
Any user - even those who are not licensed for Jira Service Management or any Atlassian products - is granted a temporary “User” role when an Assets objects custom field is added to a request type which can be accessed by end-users on a portal. This allows them to view the Assets objects fields and their values.
Jira Software, Jira Service Management, and Jira Work Management users will have temporary "Object Schema User" roles that allow them to view and edit the contents of an Assets objects custom field within issues where they already have existing edit permissions.
These roles will not count towards the total number of users on your license.
Assets in Jira Service Management is an incredibly powerful tool that records and maps the relationships and dependencies between your assets, configuration items and services. It’s great for getting a better understanding of what could have caused an incident, what impact a change could have, and for quickly accessing information about what your business owns and/or controls.
To set up Assets on your site, there are a few steps that have to be done in a specific order. This will put the foundations in place and show you how to build out your asset and service architecture.
Step 1:
Create a schema. A schema is a collection of object types and objects. This could contain your entire organization's assets and configuration items, or just a specific part – having multiple schemas can allow for different teams to manage the assets that are important to them. Learn more about structuring objects in Assets.
Start by creating just one and populate it with object types and objects. This will allow you to create object types and objects for Jira Service Management to find and show in the issue view and portal. e.g. Servers. Learn how to create schemas.
Assets also has several handy object schema templates with preset object types and attributes to get you started faster - go to Assets → Create schema and select a schema template from there.
Step 2:
Create an object type. Object types can contain several objects and their attributes. Learn how to create object types.
Step 3:
Create a few objects. You can also use these to create references (linking objects together) to start building a graph to show relationships and dependencies. Learn how to create objects.
Step 4:
Set up your Assets objects custom field. This will enable your team to see Assets objects directly from the issue view, providing context where it's needed most. Learn how to set up your custom Assets objects field.
Now that your custom field has been set up, you should know the essentials for using Assets in Jira Service Management to the full.
Next, you can use the Import feature to create multiple object types and objects from your existing database.
Was this helpful?
Still need help?
The Atlassian Community is here for you.