Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

Summary

JSM Projects has two features that allows you to customise the way that users can create issues. The first feature is Forms, these are websites that a user will use to fill out the form. When the form gets submitted it will create a new issue with the entered information. The second feature is a Widget and these are placed on your website which allows anyone who accesses your website to create new Issues. Both Forms and Widgets are found in Project Settings.

JSM Form

JSM Forms require a pre-existing Jira account to gain access to the form and any person without an account will not be able to use the form. The user will need the URL to access the form, this is found in have Forms and Widgets to enable issue creation, find them in Project Settings.

Forms are hosted within your Jira instance and are accessed through standard portal issue creation or as a direct link. Users of these forms must be authenticated existing users.

Widgets are a piece of JavaScript that can be pasted into any website and will post data into your Jira instance.

JSM Forms

The user will either complete the form as part of issue creation or fill it in directly via the URL. Forms are found through JSM Project > Project Setting > Form > Edit > Settings > Create new issues. As a Jira account is needed it means the The reporter will be set to the user that submitted the form.

Issue Creation

The fields in the form can be customised and changed so you can specify the content you would like to gather. When the forms are submitted the values are issue custom fields and will be saved into the corresponding issue fields on that Issue. The form can be shown internally within the Issue so that you can see the original content that the user entered. This can be enabled/disabled within Project Setting > Form > Edit > Settings > Issue creation > Keep form open.

...

. An example created issue with a form is below.

...

JSM Widgets

Widgets are placed onto included in your website HTML and can be used by anyone regardless of whether they have a Jira account or not. Unlike Forms, Widgets do not allow you to add or remove fields. They can only display these fields:include a fixed list of fields, below, JEMHC is not involved in the issue creation and so no post processing can be done. The reporter of the issue will be set to the user related to the supplied contact email address (users are auto created and added to the Customer role when not found).

  • Summary

  • Description

  • Attachments

  • Contact email

You can enable the users to search for all request types and search your knowledge base articles. This will require “viewing” access to be set to “anyone” in the knowledge base settings.

Customer Access

...

Example Created Issue

...

Customer Permissions

In order to allow Widgets to work JSM must allow anyone to create issues using a Widget it will require you to enable two settings. These . The two settings are:

  • “Anyone allowed on the customer access settings” within Project Settings > Customer permissions.

  • “Customers can access and send requests from the portal without logging in” within Products > Jira Service Management > Customer access.

These settings will allow all users without a Jira Account to access the Widget and create issues. When an issue is created and if the contact email does not relate relates to an existing user, JSM will create a new user with Customer permissions so that the user can create comments by replying to notifications. If the contact email does relate to a user then it will assign that user as the reporter.

Disabling Customer access when Widget is enabled

If you disable “Customers can access and send requests from the portal without logging in” once the Widget is enabled and embedded it will disable the Widget and will stop it from being shown on the website.

Issue Creation

When the request is sent from the Widget it will add the Description, Summary and Reporter to the newly created issue. Below is an example of using the Widget and the information that it shown in the Issue.

...

Widget

...

Issue Created

...

...

it will become the reporter.