Build your Catalog quickly with AI

The Catalog works best when you’ve integrated your various systems - whether that’s GitHub Teams, Slack Channels or Jira Projects - having them all connected is what brings the most value.

We’re excited to release a new bulk-editing experience, that allows you to quickly connect your various systems within incident.io, and use AI to make it even more magical.

This means you can build out your catalog and supercharge your automations so you'll be able to do things like easily route alerts, send incident updates to the right channels and even export follow-ups to the right project.

Editing in bulk

You can now edit all the entries for a particular column in bulk, using our new bulk-editing interface. This is great when you’re building out a Catalog for the first time, as it saves a load of time when you’re filling in a whole column at once.

To access bulk editing, head over to Catalog, choose a catalog type, and on the attribute you’d like to bulk edit and choose 'Edit values'.

Using AI

We’ve expanded our AI product suite to include Catalog Suggestions, enabling you to use AI to do the heavy lifting for you. Suddenly, instead of needing to use hundreds of clicks to painstakingly fill in the Slack Channel for every one of your teams, you can let AI "just do it" for you in seconds.

To access AI suggestions, head over to Catalog, choose a catalog type, and click the magic wand on the attribute you’d like to auto-fill.

After the AI has done its best, you can go through to check or change any of the responses, correct any mistakes, and add anything the AI didn’t quite figure out!

🚀 What else we’ve shipped

🆕 You can now choose to send policy reports every weekday instead of just daily, so you can avoid nagging people on the weekends
🐛 "Time to complete follow-ups" chart on the Teams Insights dashboard now renders all teams correctly
🐛 Added back the missing icon for our AI assistant in the cmd+k menu
🐛 Fixed an issue preventing scrolling on the page after closing a modal
🐛 Fixed an issue where we didn’t show a user’s name correctly if they were manually escalated to
🐛 Fixed bug that caused grouped custom fields to not group correctly in some circumstances
🐛 If an incident doesn't have the right timestamps set to calculate its duration, we won't show a misleading duration
🐛 Our new searchable timezone component now supports selecting UTC again
🐛 Removed a blank section from our API docs
🐛 Setting a 0-minute time to acknowledge on a level in an escalation path now shows 0 instead of resetting to 5 minutes
🐛 The command palette can now be clicked on, as well as navigated using your keyboard
💅 Clicking a channel bookmark for a custom field now opens the dashboard so you can quickly change the field
💅 Fixed how our Slack icon renders for schedule syncing
💅 If you send a cover request that begins in the next couple of hours, we’ll create a time-sensitive notification on iOS which is more prominent than regular ones
💅 On-call cover request notifications now include some details of the duration of the request, without having to unlock your phone
💅 The 'post announcement' workflow step will now return an error if you try to announce a private incident with it, rather than silently failing.
💅 The"firing" indicator on escalations no longer gets cut off
💅 The activity heatmap on the dashboard home page now tells you if you're viewing sample data
💅 The cards on the alerts tab of an incident now have some space to breathe
💅 We now allow you to cancel a closed incident via Slack
💅 We now hide attributes which are unset from the alerts UI when viewing an alert (edited)
💅 When an action is assigned to someone, they will be @tagged in Slack