Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 29 Next »

Error rendering macro 'excerpt-include' : No link could be created for 'Layout Editor (legacy editor)'.

Request Types module

The Request Types module lets users create JSM requests on your Refined site. The module only shows Request Types that the user is allowed to see according to their Atlassian permissions.

If you connected a knowledge base to the project in native JSM, the module will suggest articles based on keywords when a user fills in the summary field.

To help users keep track of their requests, add a My Requests module on the same page.

Due to Atlassian limitations, users always have to log in to see a portal on a Refined site (even on public sites). To keep track of this issue or vote and comment on it, click here.

Request type links on Confluence pages

Combine the power of Jira Service Management (JSM) and Confluence on your sites, by adding Request Type links to your Confluence pages. For example, this can simplify HR processes on your intranet: when reading the employee handbook, a user can quickly file a request on-page.

Add this module to a page

This module is only available if you have Refined Sites for JSM Cloud.

  1. Open the Page Builder on the page you want to edit. This can be:

  2. Hover your mouse over the desired location on the page and click the + Add module button that appears.

  3. Click Requests in the left-hand menu.

Want to direct your users to native JSM instead?

Some customers prefer to lead their users to native JSM when clicking on a request type, rather than keeping them on the Refined site. In that case, we recommend adding a link to native JSM to another module, for example an Icon module or Card module.

Edit the title

Simply click the module’s title to start writing and formatting. You can use text variables to make the text dynamic, for example to display the user’s first name.

The portal group names are set up in JSM. To edit them:

  1. Go to your JSM project.

  2. Click Project settings in the left-hand menu.

  3. Click Portal settings in the left-hand menu and go to the Portal groups tab.

Edit the settings

  1. Click the module to open its settings menu, which appears on its right-hand side.

  2. Edit the settings, which are divided over multiple tabs:

Module tab

Setting

Description

Fixed height

By default, all modules adjust their size to their content. To set a fixed height instead, fill in the desired height in pixels.

Request Types tab

Setting

Description

Project

To include all projects added to your Refined site, leave this field empty.

To show one or more specific projects, enter their JSM project IDs. Separate multiple IDs with commas.

To show dynamic content, enter a text variable:

  • Is the module placed on a Refined page? Enter $servicedeskids to show request types from all JSM projects that are grouped under this Refined Page in the site structure.

  • Is the module placed on a JSM project landing page? Enter $servicedeskid to show request types from only the landing page’s JSM project.

Portal groups and request types

  • To show all portal groups and request types, leave this field empty.


  • To show specific portal groups, add their portal group IDs.

  • To show specific request types, add their portal group ID and all request type IDs, formatted as PortalGroup:RequestType1:RequestType2:etc.

  • Separate multiple items with commas. It’s possible to add a mix of portal groups and request types.

Item layout

Choose how the user sees the portal groups: Vertically, Horizontally or as Cards.

Group style

  • Tabs

  • Sidebar

  • Dropdown

  • List

  • No groups

Item size

Choose between Small, Medium, Large, and Extra large.

Description

Choose whether the request type descriptions are always visible, or only as a tooltip (visible when the user hovers over the request type).

Find IDs

  1. Go to (yourcompany).atlassian.net/servicedesk/customer/portals.

  2. Click a portal. The project ID is in the URL. For example, when the URL ends with /servicedesk/customer/portal/13/group/48, the project ID is 32.

  3. Click a request type. The portal group ID and request type ID are in the URL. For example, when a URL ends with customer/portal/13/group/48/create/94, the portal group ID is 48 and the request type ID is 94.

image-20240423-133229.png

  • No labels