Create Catalog
Catalogs in Shoppie are the starting point of the shopping experience in Jira Service Management. They allow users to browse and request products in a clear, visual, and user-friendly way.
It is possible to create multiple catalogs for different use cases, teams, or departments, each with its own products.
Each request type supports only one catalog, so if multiple catalogs are connected to the same request type, only the first catalog will be displayed.
Create Catalog
In this step, the main settings for the catalog are configured. Products and the way they appear in the Shop view are set up later.
Name: the name will appear in both the JSM portal view and the Jira issue view.
Description (Optional): helps administrators distinguish between catalogs, especially when they are similar. Think of it as an internal note or reminder that is not visible to customers.
Select a customer portal (JSM project): Select the project where the shop will be applied.
Select a request type: the request type where the catalog will be visible. By default, the catalog will appear above the form in the selected request type within the project.
Make product prices visible & currency selection: Enables product prices to be displayed and allows selection of the shop currency from the dropdown list. Leave this setting empty when prices are not required.
AQL filter: apply an AQL filter to the entire catalog to limit or customize the items shown.
AQL (Assets Query Language) is used to filter and personalize the items displayed in the catalog. For example, by applying an AQL filter, you can control which products from the Object Schema are visible in the shop or hide products that are out of stock.
Require products in cart to create support tickets: ff enabled, it won’t be possible to create a support request when the shopping cart is empty.
Item limit: limit entire catalog to a number of selected items per request. Leave empty for unlimited.
Webhook: Defines a webhook endpoint that receives cart updates whenever changes are made. The payload includes a changelog of the latest actions together with the current cart data.
Draft & publish workflow
When Create is clicked, the catalog is saved as a draft with the selected settings.
Draft catalogs are not visible in the Jira Service Management request type until published. This allows catalogs to be prepared and reviewed before release.
Catalogs use a publishing workflow to control visibility in the Jira Service Management portal.
Published: the catalog is live and visible in the portal for connected request types.
Publish to portal: publishes the current draft version and makes it available to users in the portal.
Save as draft: saves the latest changes without updating the live version. This allows changes to be prepared before publishing.
Discard draft: removes the unpublished draft changes and keeps the currently published version unchanged.
Unpublish from portal: removes the catalog from the portal. It will no longer be visible to users until published again
Catalog visibility rules
Only one published catalog can be visible for the same Jira Service Management project and request type.
If another active catalog is already assigned, publishing a new catalog will keep it hidden. To make the new catalog visible, assign it to a different project or request type, or unpublish the existing catalog first.