...
Use the Freshservice Integration to forward Freshservice alerts to Jira Service Management. Jira Service Management 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.
...
When a new ticket is created in Freshservice, an alert is also automatically created in Jira Service Management automatically through the integration.
When the status of a triggered event is changed from 2 or 3 to 4 or 5, Jira Service Management automatically closes the alert.
If Send alert updates back to Freshservice is selected, actions for Freshservice are run in Freshservice when a chosen action is run in Jira Service Management for alerts
...
created by the Freshservice integration.
If Create Freshservice
...
tickets for Jira Service Management alert is selected, actions for Freshservice are run in Freshservice when a chosen action is run in Jira Service Management for alerts
...
with a different source
...
than the
...
integration itself.
For details on action mapping, see https://operations-help.atlassian.net/wiki/spaces/OPSHELP/pages/4259939/Integrate+with+Freshservice#Map-alert-actions.
Set up the integration
Freshservice is a bidirectional integration. Setting it up involves the following steps:
Add a Freshservice integration
...
in Jira Service Management
Map alert actions
Configure the integration in Freshservice
Add Freshservice integration
Info |
---|
If you're using Opsgenie's using the Free or Essentials plan, or if you’re using Opsgenie with Jira Service Management's Standard plan, you can only add this integration from your team dashboard as the Integrations page under Settings is not available in your Standard plan in Jira Service Management. To access the feature through Adding the an integration from your team dashboard will make team’s operations page makes your team the owner of the integration. This means Opsgenie will assign Jira Service Management only assigns the alerts received through this integration to your team only. To do that, Go to your team’s dashboard from Teams, . Follow the rest of the steps to complete the integration. |
To add a Freshservice integration in Jira Service Management:
...
Configure the integration in Freshservice
...
Expand | ||
---|---|---|
| ||
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
10. Add an Action for the event and |
...
select Trigger Webhook. 11. Paste the URL you copied while adding the integration in Jira Service Management into Callback URL. 12. |
...
Select "POST" |
...
for the request type, |
...
"JSON" for encoding, and |
...
" |
...
Simple" for content. 13. Paste the JSON from here. 14. |
...
Select Done. 15. Select Activate. 16. Add another event and set the following rule: "Note is Added" |
...
of type "Private" ( |
...
for notifications on private note). 17. Add an Action for the event and |
...
select Trigger Webhook. 18. Paste the URL you copied while adding the integration in Jira Service Management into Callback URL. 19. |
...
Select "POST" |
...
for the request type, |
...
"JSON" for encoding, and |
...
" |
...
Simple" for content. 20. Paste the JSON from here. 21. Select Done. 22. Select Activate. |
...
If you are using a new version of Freshservice
...
Expand | ||
---|---|---|
| ||
A Dispatch'r |
...
rule is needed to send Webhook notifications for |
...
new tickets, and an |
...
Observer |
...
rule to send notifications on ticket actions ( |
...
such as add note, close, reopen |
...
, and so on). |
...
Add Dispatch'r |
...
rule |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Add Observer |
...
rule |
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
Action Mapping
...
|
Map alert actions
Define mappings between Jira Service Management actions and Freshservice actions.
For alerts created by Freshservice
...
In the Send alert updates back to Freshservice section, map Jira Service Management actions to Freshservice actions when the alert source
...
is Freshservice (
...
the alert is created by
...
the integration
...
itself). For example, you can add a public comment to the Freshservice ticket
...
when the alert is acknowledged.
...
To do this,
...
define If alert is acknowledged in Jira Service Management,
...
a public comment to the ticket in
...
Freshservice
...
.
For the other Jira Service Management alerts
...
In the Create Freshservice tickets for Jira Service Management alerts section, map Jira Service Management actions to Freshservice actions when the
...
alert source is NOT Freshservice (the alert source is
...
some other integration).
...
Map one Jira Service Management action to create an issue Freshservice a ticket in Freshservice action. The Jira Service Management action doesn't does not have to be alert is created, it can be other actions as well; you can select from a list of Jira Service Management actions for this mapping. However, this rule won’t work if you’re using SSO while logging you use SSO to log in to FreshdeskFreshservice.
The actions a tag is added to the alert and a custom action is executed on alert actions slightly differ from other the rest of the actions. When you select one of these actionseither, you 'll will see an extra field to enter specify for which tags tag or for which custom action this mapping will should work.
You can enter multiple tags by separating the tags with a commacomma-separated tags. If you enter multiple tags, the mapping will work if the alert has one or more of the specified tags. You can also leave Leave the tags field empty , if you would like want the mapping to work for any tag.
If you map an a Jira Service Management action to multiple Freshservice actions, you will get an error except for the a tag is added to the alert and a custom action is executed on alert actions. You can save multiple mappings for these actions , because they will differ by the given tags and the given custom action names.
...
Expand | ||
---|---|---|
| ||
|
...
Expand | ||
---|---|---|
| ||
|
...