We are well into 2022 and are busy bringing new exciting features to market. Our customers continue to provide input into our product roadmap and many new features are based on this collaborative effort. A big thank you to our valued customers. Throughout the year we will continue to drive innovation and allow our customers, of all sizes, to implement the most advanced AIOps solution in the shortest time possible.

We've launched a feature that will help you fix errors and performance issues as a team! 🎉 With Logbook you get the full incident history. Read and leave team comments, see which notifications were sent at what time, and see team activity for changes in incident states. It's now easier than ever to see what the current state of an incident is.

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.

When an incident happens, most organizations have a way of identifying all affected services. The trouble is, it’s often a human-centered process that depends on the knowledge of key individuals or manually updated documentation. There might be a version in your alerting tool, a version in your corporate Wiki, and a different version still in your team’s head.