Get more from your Jira integration with custom field support

FireHydrant now supports incident data field mapping to Jira custom fields, including the most common epic ticket type and customer-defined fields.

Michelle Peot

When FireHydrant originally launched our Jira Cloud and Jira Server integrations, we did not support custom fields. This prevented customers who rely on Jira epic ticket types or other custom required fields from getting full value from our Jira integrations.

That has changed with the launch of Jira custom field support. We now support the most common type of Jira epic tickets and field-level mapping of Jira custom fields with FireHydrant incident data. No more duplication of effort or transcription errors, you can automate Jira epic ticket creation and custom field population directly from FireHydrant.

Epic incident types

FireHydrant supports the most common type of epic tickets, for example those implemented as part of the Jira Scrum Template. To set epic as the default ticket type for incident or action item tickets, simply use the Jira multi-project workflow to configure your Jira project as the destination. For Jira projects with epic ticket types, Epic is now selectable for incident and action item tickets (as shown below).

Jira Epic ticket support

Other custom field types

In addition to epic tickets, FireHydrant now also supports the ability to map other Jira custom fields to FireHydrant incident fields. Two mapping strategies are available:

  • Basic strategy, a direct mapping between a Jira custom field and a FireHydrant field
  • Logic strategy, a conditional mapping between a FireHydrant field and a Jira custom field

Additionally, the Jira custom fields can be configured to populate with one of two types:

  • Attribute type, which populates the Jira custom field with the exact FireHydrant incident data
  • Literal type, which populates the Jira custom field with a specified value

Let’s run through some examples.

Example: Incident Start Date and Time

In the Jira project for the MySQL service owner at your company, there is a custom Jira field, Start date, where the team keeps track of when incidents started. To populate this field with the exact FireHydrant incident start date and time, you can set up a custom field mapping using the basic strategy and attribute type as follows:

Jira custom fields basic mapping example

Example: Custom Severity Labels

The Kafka team at your company prefers to use descriptive severity labels in their Jira project instead of numbered severities to avoid misinterpretation during incident remediation. To automate this process, you can use the logic strategy and literal type. When a Jira incident ticket is created from a SEV1 FireHydrant incident, the Jira Custom Severity field will be populated with the value “Urgent”. You can add additional field mappings for the remaining severity levels.

Jira custom field logic mapping example

Get Started

For more information on configuring Jira multi-project or epics, please refer to the following user documents:

For detailed instructions on configuring Jira custom fields, visit our knowledge base document.

Weekly newsletter

No spam. Just the latest releases and tips, interesting articles, and exclusive interviews in your inbox every week.

Read about our privacy policy

Get started with the most comprehensive reliability platform on the market

Create your free account