Configure the Assets objects custom field

You can use the Assets objects custom field to view Assets objects in Jira Service Management. To choose which objects the Assets objects field will display you can configure the field in three different ways:

• use Object schema to filter objects by object schema

• use Filter Scope (AQL) to filter objects based on information from Assets

• use Filter Issue Scope (AQL) to filter objects based on information from the current issue

Use the Object schema field

Use the Object schema field to select which object schema will be linked to this Assets objects field. This field is required.

If you have selected objects from a different object schema in the Filter Scope (AQL) field, only objects in this object schema will be displayed.

Use the Filter Scope (AQL) field

Use the Filter Scope (AQL) field to filter Assets objects based upon information from Assets.

This field is optional. You cannot use placeholders in this field.

For example, if you wanted to create an Assets objects field that only displayed certain models of laptop, based on a certain manufacturer, you could enter the AQL query objectType = “Laptop” AND Manufacturer = “Apple” to show only these objects.

Use the Filter Issue Scope (AQL) field

Use the Filter Issue Scope (AQL) field to filter your data using information from within the issue itself - based on other Assets object fields or Jira system fields that contain information about the issue.

This field includes validation - correct AQL syntax will be marked with a while incorrect AQL statements will be marked with a .

This field is optional. You can enable Display a default object when this field appears in a customer portal to automatically display an object in this field.

You can use placeholders in this field. Learn more about placeholders.

Filter using object fields from within the issue

You can use the Filter Issue Scope (AQL) field to reference Assets object fields from within the issue. This can be used to link together two or more Assets object fields and create a cascading list.

For example, if you wanted to create an Assets object field that only displays certain models of laptop based on the manufacturer you’ve selected in another custom field, you would create two separate Assets object fields.

Create your first Assets object field and name it “Manufacturer”. Configure the field to show only “Manufacturer” objects retrieved from Assets by setting the Filter Scope (AQL) to objectType = “Manufacturer”.

Now create the second Assets object field and name it “Model”. Configure the Filter Issue Scope (AQL) to show only the models of laptop from the manufacturer field in the issue by typing objectType = “Laptop” AND Manufacturer = ${customfield_xxxxx.label} where “xxxxx” is the custom field ID of the “Manufacturer” custom field.

Now the “Model” field will show only the laptops that correspond to that manufacturer.

Filter using system fields from within the issue

You can use the Filter Issue Scope (AQL) field to reference system fields from within the issue like “Assignee” and “Project”.

For example, if you wanted to only show a list of laptops owned by the current Assignee, you could configure the Filter Issue Scope (AQL) field by typing objectType = “Laptop” AND "Owner" LIKE ${assignee.label}. In this case, each laptop would have an “Owner” attribute that corresponds to the name of the assignees in Jira.

Some Jira fields can hold multiple values, while others can only hold a single value. You can refer to Jira fields using either the field value label or ID:

Using placeholders with multiple values

If the field holds multiple values, the placeholder can return a single value by using an index ${customfield_xxxxx.id${1}} or it can return all of the values at once by using a query like objectId IN (${customfield_xxxxx.id${0}}) or a query like Label In (${customfield_xxxxx.label${0}}) (where "xxxxx" is the custom field ID of the "Manufacturer" custom field).