Configure an Assets object custom field
To create or edit Assets object custom fields, users must have a Jira license.
You can configure the Assets object field to display specific objects in three (3) ways:
Object schema: Filter objects by schema.
Filter scope (AQL): Filter objects based on Assets information.
Filter work scope (AQL): Filter objects based on the current work item.
Object schema field
Use the Object schema field to select the schema linked to this objects field (required). If objects from a different schema are selected in the Filter Scope (AQL) field, only objects from that schema will be displayed.
Filter scope (AQL) field
Use the Filter scope (AQL) field to filter Assets objects based on information from Assets. This field is optional, and placeholders cannot be used.
For example, to display only certain laptop models from a specific manufacturer, you could enter the AQL query:objectType = "Laptop" AND Manufacturer = "Apple"
.
Filter work scope (AQL) field
Use the Filter work scope (AQL) (formally Filter issue scope) field to filter data using information from the work item itself, such as other Assets object fields or Jira system fields.
This field includes validation – correct AQL syntax will be marked with a check, while incorrect statements will be marked with a cross.
This field is optional, and you can enable Display a default object in the customer portal to automatically display an object in the field.
Placeholders can be used in this field. Learn more about placeholders
Filter using another Assets object field
You can use the Filter work scope (AQL) field to reference another object field within the work item. This allows you to create a cascading list where the options in one list depend on the selection made in another.
For example, to display laptop models based on the manufacturer selected in another field, follow these steps:
Create an Assets object field named “Manufacturer” and set the Filter scope (AQL) to:
objectType = “Manufacturer”
Create a second Assets object field named “Model” and set the Filter work scope (AQL) to:
objectType = “Laptop” AND Manufacturer = ${customfield_xxxxx.label}
where "xxxxx" is the custom field ID for the "Manufacturer" field.
This will make the “Model” field display only laptops corresponding to the selected manufacturer.
When using the Filter Work Scope (AQL) field, you must use the custom field ID (e.g., customfield_xxxxx
) rather than the custom field name (e.g., "Manufacturer").
Note that ORDER BY is ignored when using Filter Scope or Filter Work Scope within the Assets object field.
Filter using a system field
You can use the Filter work scope (AQL) field to reference system fields from within a work item, such as Assignee and Project.
For example, to show a list of laptops owned by the current Assignee, configure the Filter work scope (AQL) field with:objectType = “Laptop” AND "Owner" LIKE ${assignee.label}
In this case, each laptop object would have an "Owner" attribute that matches the assignee's name in Jira.
Jira fields can hold either multiple values or a single value. You can refer to these values using the field's label or ID.
For example, if a custom field holds three (3) values: "bread", "bear", and "potato":
(${customfield_1223.id${1}})
will return "bread".(${customfield_1223.id${3}})
will return "potato".(${customfield_1223.id${0}})
will return "bread", "bear", and "potato"
Jira system fields are case-sensitive and must be typed exactly as shown in the table below.
Work 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 | Work 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 does not include the system field types available in Assets for Data Center.
To search these system fields, you must either:
Create Assets objects to model these fields (e.g., create a Project component Assets object) and set them as values in another custom field.
Use the field labels and/or IDs directly.
Use placeholders with multiple values
When a field holds multiple values, the placeholder can return either a single value or all values at once:
To return a single value, use an index:
${customfield_xxxxx.id${1}}
To return all values at once, use a query like:
objectId IN (${customfield_xxxxx.id${0}})
or
Label IN (${customfield_xxxxx.label${0}})
In these examples, "xxxxx" represents the custom field ID (e.g., for the "Manufacturer" custom field).
Placeholders are not supported inside an Automation flow.
Additionally, Text custom field types do not work with placeholders, as they are set values and cannot be dynamically referenced.
Was this helpful?