Assets objects custom fields
On this page:
Jira Cloud plans and Assets
Assets is a Premium and Enterprise-only feature in Jira Service Management Cloud. It's compatible with company-managed projects only.
What are Assets objects custom fields?
Assets is an asset management feature in Jira Service Management Cloud. It is designed for IT teams allowing them to connect, track and manage the assets of their teams - application services, infrastructure, hardware, people, and much more.
Visit Atlassian’s Get to know asset and service management with Assets documents to learn more.
Assets objects custom fields are configuration elements you can create in Jira Service Management Cloud to track assets and resources in your team’s service requests, incidents, and problems. For more detail, check the What is the Assets objects field Atlassian article.
To be able to create Assets objects fields in Service Management Cloud projects, you need to create Assets-specific configuration elements called object schemas, object types, and objects.
To configure and use Assets best, we advise you to follow the guidelines and steps described in Atlassian’s Starting from scratch tutorial.
Display Assets objects field values in Issue Matrix
Assets objects fields' values can be shown on Issue Matrix panels in issue screens. You just need to create Issue Matrices in your Service Management projects and include the Assets objects fields in the configuration the same way you include any other custom field.
Check out the documents for creating Issue Matrices in Service Management Cloud and Jira Cloud projects in general.
Can I use the JQL extension for Assets objects fields?
Our JQL extension is a powerful tool that offers you customized (extended) JQL syntax to refine further the data displayed in Issue Matrices.
Extended JQL syntax is supported for Assets objects fields in Service Management projects.
Use case
In this section of the document, we’ll go through an example of how to display Assets objects custom field values from different issues in a single Issue Matrix panel.
Scenario
Imagine you have a request by an employee in your Service Management project about a problem using an antivirus software product. While attempting to resolve the employee’s issue, you would like to see all employee requests related to the same piece of software and their status.
How Issue Matrix solves this challenge
You can configure an Issue Matrix panel to display information for all requests related to the same software or hardware product as the current issue you’re viewing in Jira.
Assets configuration needed for the use case
For the purposes of our example, we’re assuming that you’ve already created an Assets object schema, object types, and objects for your company’s assets like software, hardware, services, employees, etc. If not, you can learn how to create all that in Atlassian’s Starting from scratch tutorial.
Once your Assets objects are ready, you can create an Assets objects field to store software assets per user request. We named the Assets objects field Software products in our example.
We use this custom field to record your company’s software assets related to a given Service Management request. This means that when creating a request, a user can record the software products related to it in the Assets objects field on the screen.
Create a JQL Issue Matrix in your Service Management project. Refer to our guide for configuration steps and details.
In the JQL entry section of the configuration, enter an extended JQL query filtering all issues with Assets objects field value match with the currently viewed issue (see also point 1 in the image below):
"Software products" IN (${currentIssue.cf["Software products"]})Reach the Data section of the configuration, where you’re choosing the custom fields whose values will be gathered from issues and will be displayed in the Issue Matrix panel.
From the Column dropdown, choose an Assets objects custom field (see point 2 in the image below).
Choose the rest of the custom fields you would like to collect information from.
Save the configuration and open a request in your project. You should see a matrix similar to the one below:
