Enabling self-service application access requests in Jira Service Management through Application Catalogs

This guide will walk you through the steps needed to set up Multiplier's self service access request workflow feature once you've connected your identity provider.

Here's a video that demonstrates this feature:

How can I enable this magical feature?

Application catalogs are created from the Configuration screen. Navigate to Multiplier's configuration screen, accessed through the Apps > Manage your apps in the Jira nav. Once there, open the tab titled Application Catalogs.

An application catalog can be displayed on any request type, and each catalog can display a different set of applications. If you do not want to use an existing request type, go to Project Settings > Request types and click Add new request type.

Lets start by creating our first application catalog, by clicking Add New Catalog button. The catalog creation screen will be displayed.

Where will the catalog be displayed?

The first an only required field is the Request Type for which you would like to display the catalog. The catalog will be display on the Request Type's creation screen.

Which applications will be included in the catalog?

The next decision to make is which applications should be displayed in the catalog. Each application can have one category, and none, one or more tags. In the context of an application catalog, categories and tags will be called conditions. If you select at least one condition, only applications matching at least one of the specified categories or tags will be included in the catalog. If no conditions are specified, all approved applications will be displayed.

What if the application the user wants is not included in the catalog?

That is a great question. If you want the user to be able to request applications not currently listed in the catalog, you can enable the "Other" option. When enabled, the user will be able to manually enter the name of the application being requested.

In the portal, the "Other" option will look like this:

Once the application has been provisioned, can we transition the issue to another status?

Yes! You can transition the issue based on the application's categories and/or tags, or select a default transition status:

The default transition will be used if no conditional transitions have been defined, or if the application does not match the condition for any of the conditional transitions. Conditional transitions can be defined by selecting one or more categories or tags, and a target status. For instance, if you define the following conditional transition.

In this example, if the provisioned application has the tag needs_manual_work , the request issue will be transitioned to waiting for support status, regardless of the defined (if any) default transition.

Conditional transitions will always be considered before, and if no conditions matches, the default transition (if any) will be used.

Please note transition happens only if provisioning is successful.

Once you have configured the catalog, press the Create button. The catalog should be displayed on the list. To persist the changes, click the Update App Catalogs button.

To try the catalog, just open the portal creation screen for the selected request type.

Next Reading