• Products
  • Get started
  • Documentation
  • Resources

What is the Assets objects field?

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.

Creating a custom Assets objects field allows your team to access Assets objects directly from the issue view. This is a powerful feature of Assets in Jira Service Management that can help your agents get the context they need to resolve an issue or request quickly and effectively.

Adding an object (i.e. as a value) to the Assets objects custom field creates a link between an issue and an object. This then allows you to see all of the connected issues from the object view.

This is useful for incident management because you can use the graph to traverse through dependencies and understand where things have gone wrong.

It’s also useful for change management because it allows you to see the bigger picture and evaluate risk - easier to do when you can see what depends on the item you’re making changes to.

The Assets objects field functions differently in Cloud than it does in the Server/DC version of Assets. In Assets for Cloud, users cannot use an Assets object field to sort search results in a JQL query.

Still need help?

The Atlassian Community is here for you.