...
Catalogs in Shoppie serve as the
...
central hubs
...
where
...
shops,
...
powered by Jira Assets,
...
are organized. They provide flexibility and customization to meet various needs. Here's why they are essential
...
You have the flexibility to create multiple catalogs tailored to different needs or audiences.
Each catalog can be linked to distinct Jira projects, ensuring relevance and specificity. Beyond projects, you can further customize by assigning different request types to individual catalogs. This granularity ensures users find exactly what they're looking.
...
Click on the “Create a catalog” button and define basic details:
...
Name → It will appear in the JSM portal when the shop dialogue opens.
...
:
Multiple catalogs: Create separate catalogs for different use cases or audiences, ensuring each is tailored to specific requirements.
Project relevance: Link each catalog to specific Jira projects, keeping the shopping experience relevant and focused.
Request type assignment: Assign different request types to each catalog, making it easier for users to navigate and find what they need.
| Note |
|---|
It is only possible to create one catalog per request type. If you create multiple catalogs, only the first one created will be displayed. |
...
Click the “Create a catalog” button and set key settings.
| Info |
|---|
At this step, you are defining the key settings related to the catalog itself. The Assets and their display in the Shop view are not configured yet. These will be addressed in the following steps. |
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) → Project in which : Select the project where the shop will be applied toand made visible.
Select a request type → Request type that is associated with the shop. Click on : The request type where the catalog will be visible. The catalog will appear above the form in the selected request type within the project. Only request types from the selected project will open a shop catalogbe available.
Currency → Currency for the items in the shop. Select desired currency from the dropdownlist of currencies supported
AQL filter → Define an AQL filter that will be applied to the entire catalog
Item limit → Configure the amount of items that can be selected and added to the cart for the catalog
...
Configure Catalogs
Click on the “Customize catalog” 
, and follow next steps:
...
...
...
...
(Optional): Select the currency for shop items from the dropdown. Leave it empty if prices are not needed.
AQL filter: Apply an AQL filter to the entire catalog to limit or customize the items shown.
| Info |
|---|
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: If enabled, it won’t be possible to create a support ticket when the shopping cart is empty.
Item limit: Limit entire catalog to a number of selected items per request. Leave empty for unlimited.
| Info |
|---|
Clicking the "Create" button will create a catalog with the selected options. The catalog will not be visible in the JSM request type yet, as it remains in "Draft mode" until manually published. |
...