Changelog

New updates and improvements to incident.io

Stay up to date — Follow us on Twitter

Weekly Update

Let it sync in

This week we're doubling down on Jira; helping you connect incident.io to your existing processes.

Auto-export incidents to Jira

We know that a lot of our users use Jira, for a wide variety of use-cases surrounding incidents. We want to make it really easy to integrate incident.io with your existing processes, so that its simple and safe to start using incident.io. It also means you can keep using all your existing reporting processes without having to start all over again.

You can now configure your incidents to create a ticket in Jira whenever an incident reaches a pre-defined severity, by editing your workflows settings.

The ticket will have a link back to the incident.io homepage so you can easily move between the two:

View incident ticket in Jira

P.S. We want to make sure you don't get an avalanche of Jira tickets, so test incidents will never create Jira tickets.

What we shipped

We've spent a lot of the week working on our internal debugging tooling, so we can identify and fix issues quickly. We've also worked on a few things you might notice:

  • 💅 We now support freetext fields when exporting to Jira

  • 💅 The Jira export modal now walks you through selecting a project and then an issue type, so it's easy to see what fields you need to fill in.

  • 🐛 If you pin a message that's in a thread, it'll now show up in the timeline in the Web UI and Postmortem

  • 🐛 If you pin a message from google hangouts, that will now get added to the timeline

  • 👷 We made our error reporting, stack traces and logs much more useful internally, to help us fix any issues that crop up even faster!

  • 👷 We invested some time into optimising our build and release pipeline, we can now ship changes to you in half the time 🚀


Start your free 14-day trial, no credit card necessary.