Learn about apps and functionalities which can be used with My Requests Extension.
Here you can read about the apps from Deviniti and third-party vendors that are compatible with My Requests Extension.
The My Requests Extension app is compatible with Extension for Jira Service Management and it enables users to display Bundled Fields as both Columns and Criteria on Requests page.
In the table below you can see the details of this compatibility.
| Field | Columns | Criteria |
|---|---|---|
| Bundled Fields from Extension for Jira Service Management |  |
|
In Fields configuration, Bundled Fields are displayed as a field with Text field (multi-line) type where its values are displayed as a plain text. Due to the technical limitations, it’s the only way to render this field.
You can use the My Requests app together with Assets in Jira Service Management to set Assets objects custom field as Columns as well as Criteria and help customers organize their requests on Requests page.
Bear in mind that in order to use Assets in Jira Service Management it’s required to upgrade to the Jira Service Management Premium plan.
By using the Assets objects custom field it’s possible to configure the field only with Object schema and Filter Scope (AQL) while Filter Issue Scope (AQL) and Object attributes to display on issue view aren’t supported.
My Requests Extension for Jira Service Management allows you to use Assets objects custom field which can be displayed on Requests page as Column.
By accessing Fields configuration you can use the toggle to enable Assets objects custom field as Column.
When the toggle is turned on, the users of your Requests page will see Assets objects custom field when selecting the columns’ configuration.
Once the columns configuration is set, the users of your Requests page can display Assets on the list with requests.
The My Requests Extension app also enables you to display Assets objects custom field on Requests page as Criteria.
In order to use Assets objects custom field as Criteria you need to establish the Assets API connection. To learn more, navigate to the Settings section.
By accessing Fields configuration you can use the toggle to enable Assets objects custom field as Criteria.
Once the toggle next to Criteria in Fields configuration is enabled, Assets objects custom field becomes available as the filtering criterion when displaying requests.
By selecting criteria for filtering, the users of your Requests page can display and use Assets.
The Assets objects custom field used as Criteria respects context field configuration related to Applicable contexts for scheme. That’s why, by using filtering criteria on Requests page users can display only assets from contexts to which they have access.
If you can’t find the answer you need in our documentation, raise a support request. Include as much information as possible to help our support team resolve your issue faster.
