• Products
  • Get started
  • Documentation
  • Resources

Configure the Assets objects custom 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.

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.

When using the Filter Issue Scope (AQL) field, you must use the custom field ID (“customfield_xxxxx”) to identify custom fields and not the custom field name (“Manufacturer”).

ORDER BY is ignored when using Filter Scope or Filter Issue Scope within the Assets object field.

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:

Jira system filed are case-sensitive and must be typed exactly as below.

Issue key

Label / Description

Multiple

Type

${key.id}

${key.label}

assignee

Assignee

false

ApplicationUser

userKey

Display Name

dueDate

Due Date

false

Date

dueDate

dueDate

fixVersions

Fix Versions

true

String/Custom Assets object

Id

Name

issueType

Issue Type

false

String/Custom Assets object

Id

Name

components

Components

true

String/Custom Assets object

Id

Name

priority

Priority

false

String/Custom Assets object

Id

Name

project

Project

false

String/Custom Assets object

Id

Name

reporter

Reporter

false

ApplicationUser

userKey

Display Name

resolution

Resolution

false

String/Custom Assets object

Id

Name

summary

Summary

false

String

summary

summary

Assets in Jira Service Management does not include the system field types that are included with Assets for Assets in Jira Service Management Data Center.

If you want to search on these system field types, you must either create Assets objects modelling these fields (ie. you will need to create your own Project Component Assets object) and set them as a value in another custom field, OR you can use the field labels and/or IDs.

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).

The use of placeholders is not supported inside an Automation flow.

Text custom field types do not work with Placeholders as they are set values.

 

Still need help?

The Atlassian Community is here for you.