Get started with Jira Service Management for admins
Your first stop for learning how to get started with Jira Service Management.
This article highlights a new alerting feature that's natively available in Jira Service Management which is gradually rolling out to some Jira Service Management Cloud customers. It may not yet be visible or available on your site.
Use the integration to send Salesforce Service Cloud cases to Jira Service Management with detailed information. Jira Service Management acts as a dispatcher for Salesforce Service Cloud cases, determines the right people to notify based on on-call schedules– notifies via email, text messages (SMS), phone calls, and iOS & Android push notifications, and escalates alerts until the alert is acknowledged or closed.
This document describes how to configure the integration and details of data that Jira Service Management receives from Salesforce Service Cloud.
When a case is created by Salesforce Service Cloud, an alert is created in Jira Service Management.
When the case's state is changed to Working in Salesforce Service Cloud, the corresponding alert is acknowledged in Jira Service Management.
When the case's state is changed to Closed in Salesforce Service Cloud, the corresponding alert is closed in Jira Service Management.
If Send Alert Updates Back to SalesForce Service Cloud is enabled, actions for Salesforce Service Cloud are executed in Salesforce Service Cloud when the chosen action is executed in Jira Service Management for alerts which are created by the Salesforce Service Cloud integration.
These action mapping features are explained in detail in the Action Mapping Feature section below.
Salesforce Service Cloud is a bidirectional integration. Setting it up involves the following steps:
Add a Salesforce Service Cloud integration in Jira Service Management
Configure the integration in Salesforce Service Cloud
Bidirectional integrations aren’t supported in Free and Standard plans. All the other integrations are supported at a team level in Free and Standard; however, for their outgoing part to work, you need to upgrade to a higher plan. To add any integration at a site level through Settings (gear icon) > Products (under JIRA SETTINGS) > OPERATIONS, you need to be either on Premium or Enterprise.
Adding an integration from your team’s operations page makes your team the owner of the integration. This means Jira Service Management only assigns the alerts received through this integration to your team.
To add a Salesforce Service Cloud integration in Jira Service Management, complete the following steps:
Go to your team’s operations page.
On the left navigation panel, select Integrations and then Add integration.
Run a search and select “Salesforce Service Cloud”.
On the next screen, enter a name for the integration.
Optional: Select a team in Assignee team if you want a specific team to receive alerts from the integration.
Select Continue.
The integration is saved at this point.
Expand the Steps to configure the integration section and copy the API URL.
You will use this URL while configuring the integration in Salesforce Service Cloud later.
Select Turn on integration.
The rules you create for the integration will work only if you turn on the integration.
To configure the integration of Salesforce Service Cloud with Jira Service Management, complete the following steps:
In SalesForce Service Cloud, select Settings > Developer Console.
On the Developer Console page, select File > New > Apex Class.
Copy-paste jsmClass.apxc.
Select Save.
On the Developer Console page, select File.
Select New > Apex Trigger and copy-paste jsmTrigger.apxt.
Paste the API URL previously copied from Jira Service Management into the endpoint field in the trigger function.
Select Save.
Go back to the SalesForce page and select Setup.
Go to Setup > Security > Remote Site Settings.
Add a new remote site and name it JSM.
Paste the URL copied previously into Remote Site URL.
Select Save.
To use the forwarding feature of the integration, add "jsm-alias" field to Cases.
In Jira Service Management, you can define mappings between Jira Service Management actions and Salesforce Service Cloud actions.
Use this section to map Jira Service Management actions to Salesforce Service Cloud actions when the source of the alert is Salesforce Service Cloud (i.e When the alert is created by Salesforce Service Cloud integration.)
Map different Jira Service Management actions to different Salesforce Service Cloud actions. For example, set case status to Working in Salesforce Service Cloud, when the alert is acknowledged. In order to do this, define If alert is acknowledged in Jira Service Management, set case's status to Working in Salesforce Service Cloud. mapping in Send Alert Updates Back to Salesforce Service Cloud section.
a tag is added to the alert and a custom action is executed on alert actions differ from other actions. When one of these actions is selected, an extra field appears to enter for which tags or for which custom action this mapping works.
Enter multiple tags by separating the tags with a comma. If multiple tags are entered, the mapping works if the alert has one or more of the specified tags. Leave the tags field empty to have the mapping to work for any tag.
If an Jira Service Management action is mapped to multiple Salesforce Service Cloud actions, an error occurs except for the a tag is added to the alert and a custom action is executed on alert actions. Save multiple mappings for these actions because they differ by the given tags and the given custom action names.
Use this section to map Jira Service Management actions to Salesforce actions when the source of the alert is NOT Salesforce (i.e When the alert is created by another integration.)
For this purpose, use Create Salesforce Issues for Jira Service Management Alerts section. In order to use this functionality, map one Jira Service Management action to create an issue Salesforce action. The Jira Service Management action doesn't have to be alert is created, it can be other actions as well.
a tag is added to the alert and a custom action is executed on alert actions differ from other actions. When one of these actions is selected, an extra field appears to enter for which tags or for which custom action this mapping works.
Enter multiple tags by separating the tags with a comma. If multiple tags are entered, the mapping works if the alert has one or more of the specified tags. Leave the tags field empty to have the mapping to work for any tag.
If an Jira Service Management action is mapped to multiple Salesforce actions, an error occurs except for the a tag is added to the alert and a custom action is executed on alert actions. Save multiple mappings for these actions because they differ by the given tags and the given custom action names.
Was this helpful?