Add FreshService as a Ticket destination

[allenhouchins]

prospect-pingouin: https://fleetdm.slack.com/archives/C07GLME5P7C/p1728329669900549

• @noahtalerman: User requested this because my organization picked FreshService as my ticketing tool (instead of Jira/Zendesk) and I want a convenient, one-click, way to create tickets for failing policies and vulnerable software like Fleet can for Jira/Zendesk.
  • @noahtalerman: In the interim the user can use webhooks in Fleet to create tickets in FreshService.
  • @noahtalerman: Eventually Fleet could add FreshService as a first-class ticket destination.

---

[noahtalerman]

Problem

Admins want to be able to configure FreshService as a ticket destination for policy failure automation similar to how we support Jira and Zedesk today.

What have you tried?

I discovered an older request for this feature: https://github.com/fleetdm/fleet/issues/6602

Admins have the ability to use webhooks in the interim but are seeking an out of the box solution that doesn't require them configuring, performing on-going maintenance, and possibly needing another tool like Tines.

Potential solutions

Create a FreshService connector similar to our current Jira and Zendesk integrations.

What is the expected workflow as a result of your proposal?

An admin will be able to select FreshService as a ticket destination under Settings > Integrations > Ticket destinations and then configure policy automation accordingly.

[noahtalerman]

Hey @allenhouchins I pulled this request off of feature fest b/c it doesn't meet the criteria for prioritization: https://github.com/fleetdm/fleet/pull/23184/files#diff-c99d12c3af50c0c2aca2b9ef7597c02ccfe87678291956ff0b2e83d63978ea38R370