Ticketing Settings

In addition to the settings for specific ticketing providers, FireHydrant has some additional settings users can configure for Incidents and Follow-Ups that are configurable at Settings > Ticketing settings in the UI.

Follow-Up Ticket Priorities

When creating Follow-Up tickets, users can specify the Priority. Combined with custom field mapping for specific ticketing providers, these priorities can then be mapped to an external ticketing provider's priority values, ensuring that tickets created in external systems are set to correct values for prioritization of work.

Visit the documentation for your respective ticketing provider for more information on field mapping.

General Ticketing Settings

Default project for incident tickets

This chooses a default external ticketing integration project for two items:

• Create an Incident Ticket Runbook step
• Creating a Follow-Up with an emoji

Most users will not use the "Create an incident ticket" Runbook step. FireHydrant recommends using the specific Runbook steps for their respective ticketing providers:

• Create an Asana Task
• Create a Jira Issue
• Create a Shortcut Issue

The only exception to this is for organizations using ServiceNow, who will need to use this step since there is no dedicated "Create a ServiceNow ticket" Runbook step.

Follow-up Title Template & Description Template

Organizations can fill in pre-templated content for Follow-up tickets. When creating a Follow-up ticket from either Slack or the Command Center web UI, this content will be prefilled in the input boxes, making it easier to quickly create tickets.

📘

Note:

These fields support Liquid templating.