Learn how to display Assets in Dynamic Fields.
It’s possible to use the Extension for Jira Service Management app together with Assets in Jira Service Management. This compatibility enables you to dynamically display the Assets objects custom field in request forms visible to the Customer portal users. For administrators, adding and configuring the Assets objects custom field is possible only with active Jira Service Management Premium Plan and established connection with Assets API.
Deviniti’s Rovo Assistant provides access to a virtual assistant that helps you with configuration, installation, and troubleshooting, enabling quicker and faster navigation through documentation. See Deviniti’s Rovo Assistant documentation or find it on the Atlassian Marketplace for more information.
Before you start configuring Assets objects custom field in the Customer form extension configuration, make sure you’re using the Jira Service Management Premium Plan. Next, establish your connection with Assets API.
To learn about establishing connection with Assets API navigate to the Connect to Assets API section.
Once you’ve successfully established your connection with Assets API, you can make your Assets objects custom field dynamic by accessing the Customer form extension configuration.
To learn about configuring Dynamic Fields with Assets, watch the Quick Guide below.
Thanks to the configuration added in Customer form extension it’s possible to use Dynamic Fields together with Assets by raising requests on the Customer Portal.
Your Assets objects custom field can be displayed in a request form in response to user input in previous fields of that form.
The app supports the Object schema and Filter Scope (AQL) configurations related to Assets objects field configuration by default.
By accessing Extension for JSD > Assets API > AQL settings, it’s also possible to enable the configuration of Filter Issue Scope (AQL).
The AQL settings feature is available only for the Extension for Jira Service Management users with the Advanced edition of the app.
To learn more about App Editions, navigate to official Atlassian documentation.
With AQL settings you can manage the Filter Issue Scope (AQL) configuration any time.
By default, the toggle next to Use AQL settings is turned off. That’s why your Assets objects custom fields configured as Dynamic Fields can’t be affected by Filter Issue Scope (AQL).
When the toggle next to Use AQL settings is turned on, your Assets objects custom fields configured as Dynamic Fields respect the Filter Issue Scope (AQL) settings. As a result, you can filter objects based on issue-related data.
Bear in mind that by using Assets objects as Dynamic Fields with the Filter Issue Scope (AQL) configuration you can use only the fields that are supported by the app. Extension for Jira Service Management supports configuration of the following field types:
To learn about configuring Assets objects custom field with the use of Filter Issue Scope (AQL), navigate to official Atlassian documentation.
