...
Expand | ||
---|---|---|
| ||
10. Add an Action for the event and choose select Trigger Webhook. 11. Paste the URL you copied while adding the integration in Jira Service Management into Callback URL. 12. Set Select "POST" as for the request type, Encoding "JSON" for encoding, and content "AdvancedSimple" for content. 13. Paste the JSON from here. 14. Click Select Done. 15. Select Activate. 16. Add another event and set the following rule: "Note is Added" Type of type "Private" (For Private note notificationsfor notifications on private note) 17. Add an Action for the event and choose 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. |
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
|
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 source of the alert is Freshservice (
...
the alert is created by
...
the integration
...
itself). For example, you can add a public comment to 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 alert section, map Jira Service Management actions to Freshservice actions when the source of the alert
...
is NOT Freshservice (the source of alert 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 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.
...