FireHydrant April 2021 Product Updates: Incident Tags & Customizable Slack Incident Modals

Learn more about how incident tags can help you store more metadata and about our new customizable Slack incident modal.

Julia Tranprofile image

By Julia Tran on 4/23/2021

We're excited to announce the release of two new features this month: customizable Slack incident modals and Incident Tags. Keep reading to more about how they can help your teams manage incidents better!

Declaring incidents, your way

At FireHydrant, we want to give you the option to customize how incidents get declared to fit your current workflow. The new customizable Slack incident modal enables you to easily configure which fields you would like to appear in your modal, if you have requirements that differ from the default settings.

Configurable fields include: 

  • description - text area field that maps to incident description

  • summary - 255 character capped input field

  • customer_impact_summary - text area field that maps to incident customer impact

  • severity - single select field that maps to incident severity. A blank value will use FireHydrant's severity matrix to set the severity automatically

  • impacts_services - multi-select field that allows for adding services and their degradation condition

  • impacts_environments - multi-select field that allows for adding environments and their degradation condition

  • impacts_functionalities - multi-select field that allows for adding functionalities and their degradation condition

  • incident_tags - multi-select to add tags to an incident (you didn’t hear? Keep reading!)

Learn more and find various modal recipes in the Help Center to start customizing your new incident workflow in FireHydrant today. 

Tag, you’re it

Have you ever tried pulling a report, only to come out of it with more questions than answers? We have, and that’s why, at FireHydrant, we can’t emphasize the importance of clean, reliable metadata enough. Metadata is the foundation for effectively defining the scope of your search and easily getting answers, and that starts with tags.

We’ve added Incident Tags to empower you to store more metadata on your incidents. This makes it easier to query and get actionable insights compared to traditional labels. Now, with Incident Tags, you can tag incidents, filter by tags, and even automate Runbooks based on tag conditions. 

Some incident tag examples include: 

  • Cause codes

  • Customer impact conditions

  • Types of incidents

Learn about all of the ways you can add tags to incidents in FireHydrant, how to query by tags in the API and Incidents List, and how to set Runbook conditions using tags in our Help Center

See FireHydrant in action

See how service catalog, incident management, and incident communications come together in a live demo.

Get a demo