Wonderful Workflows

Weekly Update

After many weeks of work, we're delighted to announce the latest feature of the incident.io platform: Workflows. Configure your processes once, and we'll make sure you follow them, every time ✨.

Workflows allow you to automate certain actions and behaviours based on specific triggers. We provide a set of building blocks which you can put together to encode your organization's processes into incident.io.

That means you can now:

  • Automatically page the right person depending on the incident type.
  • Build runbooks by creating lists of actions at the start of an incident.
  • Prompt your Incident Leads to go through a Decision Flow if they mention a potential data breach.

Check out our blog post for more details on what Workflows can do, or jump straight to the app to get started.

What we shipped

  • 🆕 You can now encode your processes into incident.io using Workflows.
  • 💅 You can now filter all dropdowns in the app by starting to type in them, including when exporting actions to an issue tracker (thanks for the nudge on this, Ubie).
  • 💅 We now show user avatars when exporting issues to Jira, Github or Linear.
  • 💅 You can now see both full names and usernames when exporting an action to GitHub.
  • 💅 We've tidied up the settings navigation so it's easier to find what you're looking for.
  • 💅 We've added an RSS feed to our blog so you can subscribe here.
  • 💅 You can now search for an incident by its ID (e.g. by searching 139 you'll get INC-139).
  • 💅 We no longer show all participants on the incident homepage by default: we'll just show a few and allow you to see the rest by clicking 'Show more'.
  • 🐛 You can now unset a call link from Slack (it didn't used to allow you to, sorry folks.)
  • 🐛 Links to external issue trackers will now open in a new tab.

Modern incident management, built for humans