Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Excerpt

...

nameLimitation
Note

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.

Insert excerpt
My Requests & My Approvals modules
My Requests & My Approvals modules
nameOnly for JSM
nopaneltrue

Request Types module

The Request Types module lets users create JSM requests on your Refined site. It lists all The module only shows Request Types that a the user is allowed to see in a JSM project. Please note that anonymous users have to create an account to file a ticketaccording 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, you can add a My Requests module on the same page.

Want to direct your users to native JSM instead?
We understand some customers want 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 using a Navigation module instead.

...

...

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

Info

This module is only available if you have installed Refined for Jira Service Management Cloud.

...

  1. Go to a landing page on your

...

  1. site

...

  1. .Go to

  2. the Page BuilderClick the Edit page button.

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

  4. Click Requests in the left-hand menu.

  5. Select the Request Types module.

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 (heading), to edit it. There are various formatting options, including paragraph/heading styles. Tip: use text variables to make the text dynamic, for example to display the user’s first name.

Edit the portal group names

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. Select Click the module to see open its settings menu, which appears on its right-hand side.Click the Cogwheel.

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

Module tab

Setting

Description

Background

Add an Image, Color, or Gradient as background – or turn off the background by selecting None.

There are multiple ways to pick a color:

  • Select the shade and hue at the top of the popup.

  • Enter an RGB, RGBA, or hex code.

  • Click the eyedropper icon to select a color from anywhere on the page (available in the browsers Firefox and Edge).

  • Click one of the recently used colors.

Use the vertical slider in the middle of the popup to control the color’s opacity.

Fixed height

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

Request Types tab

If you placed this module on a JSM project page, enter the text variable $servicedeskid

Setting

Description

JSM Portal ID

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

JSM project.To
  • are grouped under this Refined Page in the site structure.

  • Is the module placed on a JSM project landing page? Enter $servicedeskid to showrequest types from

another JSM project, specify its JSM Portal ID. You can only use JSM projects that are added to your site in the Site Builder.

Portal Group IDs

Leave this field empty to show all Portal Groups in this particular JSM project.

To show only content from one or more specific groups, add their Portal Group IDs. Separate multiple IDs with commas
  • 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 Group(s): vertically, horizontally or as cards.

Display option

  • As tabs

  • As dropdown

  • By group

  • As sidebar

    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.

    Display description

    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

    ...

    titleFind a JSM portal ID

    To find a JSM portal ID:

    ...

    Go to your JSM project.

    ...

    Click Channels > Portal in the left-hand menu.

    ...

    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/

    ...

    1. 13/group/48, the project ID is 32

    ...

    titleFind a Portal Group ID

    ...

    Go to your JSM project.

    ...

    Click Channels > Portal in the left-hand menu.

    1. .

    Once you know which Portal Group’s ID you need:

    1. Click

    ...

    1. a

    ...

    1. request type. The

    ...

    1. portal group ID and request type ID are in the URL. For example, when a

    ...

    1. URL ends with customer/portal/

    ...

    1. 13/group/48/

    ...

    1. create/94, the portal group ID is 48 and the request type ID is 94.

    ...