FAQ

FAQ

As a Forge app, Shoppie meets the requirements for participation in Atlassian’s Cloud Security Participant program and is enrolled in the Marketplace Bug Bounty program, supporting continuous security testing and responsible vulnerability disclosure.

In addition, Caelor maintains an ISO/IEC 27001 certified Information Security Management System, demonstrating a structured and internationally recognized approach to information security, risk management, and continuous improvement.


Can you provide a list of the actual user permissions that Shoppie uses and requires?

The scopes the app is requiring is what scopes are granted to the application. Shoppie is not changing the users permissions in any way, user permissions are handled inside Jira, Jira Service Management etc.
Shoppie is requesting these scopes, and by installing the app, the Admin is granting these scopes to the application. You can find the list of scopes and their descriptions on this page: https://developer.atlassian.com/cloud/jira/platform/scopes-for-oauth-2-3LO-and-forge-apps/#scopes

- manage:jira-configuration - write:jira-work - storage:app - manage:jira-webhook - read:jira-work

What version of Forge is Shoppie built on?

Atlassian is not providing an option to choose a version of Forge, instead Atlassian is handling the versioning. Forge is a SaaS (Software-as-a-Service) built on AWS. By using Forge, it would safe to assume that Shoppie is using the latest Forge version.


Can the access permissions for Shoppie be locked down further by site or project admins without interfering with Shoppie functionality?

The access permission of Shoppie is heavily relying on the email and token of the user who provided it. If this user doesn’t have permissions which Shoppie needs in order to access data it requires, then the app would not work as expected.


Is Shoppie available for Data Center? If not, are you planning to release it for DC?

Shoppie is currently not available for Data Center. We are always listening to feedback from our users and assessing demand for our products across different platforms. At present, there isn't significant demand for Shoppie on Data Center, but we continue to evaluate user needs and market trends. Please let us know if this is something you would be interested in, as your feedback is valuable in guiding our future plans.


Do I need an admin permissions to configure Shoppie?

Site administrators need to create an API token that is required for the initial configuration of Shoppie. Once this token is added and saved, Jira administrators can take over the setup process. For more detailed instructions and information, please visit our documentation: Shoppie Setup for Admins.


Can I assign a catalog to multiple request types?

It is not currently possible to assign a single catalog to multiple request types directly. However, you can easily duplicate catalogs and then assign these duplicates to different request types. This method allows for flexibility while managing various service requests.


Do I need a Premium plan to use Shoppie in Jira Service Management?

No. Shoppie is now available for all Jira Service Management plans.

Previously, Shoppie required Premium or Enterprise because it relies on the Assets feature, which was limited to higher-tier plans. Since Atlassian has expanded Assets availability across all Jira Service Management plans, Shoppie can now also be used on Standard, Premium, and Enterprise plans.


Can I build a custom shop without using Assets?

No, building a custom shop within Shoppie requires the use of Assets. Assets is an integral part of the Shoppie infrastructure, providing the necessary features and functions to manage and organize shop items effectively.


Is Jira Assets the only database that Shoppie can connect with to pull data?

Yes, currently, Shoppie is designed to integrate exclusively with Jira Assets. This integration allows for seamless management and organization of shop items directly within the Jira environment.


Can I purchase items through Shoppie using a payment solution?

No, Shoppie does not currently support purchasing items through a payment solution. It is designed for internal use within organizations to manage and order inventory or assets effectively.


Can I customize the Shoppie interface to match my branding?

While many parts of Shoppie adhere closely to Atlassian's design guidelines to ensure a consistent user experience, some elements of the interface are customizable. This allows you to align aspects of Shoppie with your organization's branding to some extent.


Does Shoppie support Assets custom fields?

Yes, Shoppie supports custom fields from Assets. These fields are utilized for automation and can be integrated with REST APIs, enhancing functionality and enabling more sophisticated data handling and operations within Shoppie.


Can Shoppie help with tracking and managing asset availability?

Yes, Shoppie includes features for tracking in-stock items and displays stock availability to help manage asset availability efficiently. This functionality ensures that you can always monitor the status of your assets directly within the platform.


Is Shoppie available in other languages?

Yes, Shoppie is currently available in English and German. We are planning to add more of the most popular languages in the coming months to better accommodate our diverse user base.


Does Shoppie support automation? Can automation be built into Shoppie features?

Yes, Shoppie supports automation and allows for automation to be built into its features. All related processes and capabilities are well-documented to ensure ease of implementation and effective use.