The “Configure” tab offers a detailed configuration for each category. Each category is linked to a unique object type from Jira Assets. This design ensures that every category has its bespoke settings, mirroring the intricacies of its associated object type.
In the Configure tab the following options are available:
Object schema* → Select an object schema from which the object types will be filtered.
Included object type* → Select an object type to import as a catalog category.
AQL filter → Optional AQL filter to further narrow down the asset selection. e.g owner = currentUser()
Custom field to map to → Map category with an existing Assets custom field. Multiple object types can be added to a category. Objects from this category will be saved in this 'Assets' custom field when a customer request is submitted.
Name and icon → You can rename the category name and change the icon. Default value is what is defined in Jira Assets.
No price text → Enter custom text for items without a price.
Item limit → Limit the amount of items that can be selected from the category to one item.
.gif?version=1&modificationDate=1707732208732&cacheVersion=1&api=v2&width=340&height=347)
Only Assets custom fields will be displayed in the dropdown.
Default attributes
Name* → When configuring a catalog in a portal view, the 'Name' attribute is required. It is mandatory to define the 'Name' for each catalog. Without it, you cannot proceed further in the setup process.
Short Description → While the 'Short Description' is optional, it's beneficial for users. It provides a quick insight into the product without delving into the detailed view. When users hover over a product, the short description pops up, offering a glimpse of the product's highlights.
Price → The 'Price' attribute is optional in the catalog. If left undefined, users will see a label marked "No Price" when viewing the product. This ensures clarity for users when browsing products without specified pricing.
Price attribute needs to be FLOAT or INT data type in Assets.