July 25, 2022

New and Improved Integrations, Easier Service Catalog, and Continued Improvements to Slack App

Updates to the Service Catalog

  • Improved Functionalities view inside Service Catalog: Our Functionalities feature inside Service Catalog has a whole new look with lots of new features. The Functionalities overview, as well as detail pages, have new incident information views to quickly see what is impacted. This release also unlocks the ability for functionalities to do the following: Assign Owning & Responding Teams, Link third party Services, Auto-Alerting, new Related Service Tab, Labels, External Links, and other meta-data.
  • Managing Service Editing Permissions by Owning Team: You can now limit access to editing or deleting services to specific teams and their members. This is so you can have confidence in your service catalog definitions remaining protected. To activate this permission feature, assign an Owning Team to a Service. To learn more see our Editing Permissions documentation.

Updates to the Slack App

  • New slack command: /fh page functionality: Linking a functionality to a third party integration service will allow you to page this functionality via slack. Head into slack and type in /fh page functionality. This will populate a dropdown list of all functionalities with integration links configured. Select the functionality you would like to page. FireHydrant’s slack bot will fire off a page to the escalation policy linked to this functionality.
  • Updated the Slack message for assigning a task list: We updated the incident channel and DM messages for adding a task-list to an incident and assigning it to a responder.
  • Updated the /fh add task-list command modal: This change adds to improving and unifying our task list experience. We have rebuilt the tasks list modal and added command summaries to other parts of our task list experience, we wanted to do the same here.
  • Updated the Role Assignment DM to use BlockKit: This release replaces the message that a user receives when being assigned to a role in an incident to match our new design styling.
  • Updated the team suggestion message in the incident channel: If you add an impacted service to an incident, and that service has a responding (not just owning) team, we send a suggestion message about assigning said team to the incident.

Introducing our new Zendesk integration To more easily capture customer impact FireHydrant Enterprise tier users can now integrate with Zendesk Support. Our initial release allows Zendesk ticket linking to FireHydrant incidents. To get started see our Zendesk integration documentation. Stay tuned for enhancements coming next quarter, including capturing impacted customers and automating status updates back to support tickets.

Jira integration admin improvements

  • We’ve made several changes to clarify the difference between global Jira integration authorization and account linking. Account linking is used to associate individual users to their corresponding Jira account for Jira ticket creator attribution. Under User > My Account, the Linked Account section now uses the verbiage Link.
  • Global Jira integration reauthorization is required to reauthorize the Jira integration connection when Atlassian tokens are rotated. Only the person/account who set up the Jira integration can reauthorize the global integration. This person/account is now displayed on the Jira integration settings. If that person is logged in, they can now also reauthorize the global integration connection from that screen.
  • Lastly, we’ve added a new Jira troubleshooting document that details self-service actions users can take to diagnose and correct common Jira fault scenarios.

See FireHydrant in action

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

Get a demo