Export to any issue tracker from Slack

Previously, you could only export follow-ups to Jira directly from Slack. Now you can export to any connected issue tracker without leaving your incident channel.

This means less context switching during incidents - create the follow-up, export it, and carry on with your response, all from the same place.

Follow-up labels

You can now tag your follow-ups with labels, and we'll sync these back from your issue tracker. This opens up some useful workflows:

Route follow-ups automatically - Use labels in your auto-export configuration to send follow-ups to the right place. Security follow-ups can go to your security board in Jira, infrastructure tasks to your engineering board in Linear.

Tag follow-ups as they're created - No more having to jump into your issue tracker afterwards to categorise things. Tag them upfront so you can easily find all the follow-ups related to Postgres.

Filter follow-ups in incident.io - Use the same labels you use in your issue tracker to filter your follow-ups in our UI, and see them alongside your rich incident data.

Choose responding language in call routing

You can now pick the language you would like to use when responding to inbound calls in live call routing, instead of defaulting to English. Simply go to ‘Edit call route’ and select your preferred language. If you find the language you want isn’t supported, just ask customer support and we’ll add it!

What else we’ve shipped

New

We now show managers for OpsLevel Teams in Catalog, so you can do things like automatically invite the related team's manager

Improvements

We've made some performance improvements that mean previewing the alerts for an alert route are now a little faster
Teams homepages now refresh data in the background, ensuring that your active incidents are always up to date
We've made some UI changes to the escalation path editor which makes round robin options and "page all users on schedule" options a little easier to configure
We've made it clearer when viewing an escalation if a user wasn't notified via Slack or Microsoft Teams due to them not having an associated account on those platforms
We'll now promote 'exact' matches in the cmd+k search if you search by an incident reference number
Changed 'Name' to 'Incident Name' on our declare incident form to reduce confusion
Tightened up the display options on incident list so they're more concise
We've removed custom field warnings and suggestions when viewing previous versions on alert routes
Announcement messages in Slack now show a person's display name of people and link to their profile

Bug fixes

If you mirror schedules into another provider, we now proactively sync the schedule every day, so if you create an override more than 2 weeks away, you won't have to wait for the next shift change for that to be reflected
Fixed bug where we were incorrectly saying you weren't on call while in the mobile app
Fixed bug where we weren't using Catalog rank to sort options in incident custom fields
We've fixed a bug where the escalation timeline would occasionally repeat timeline gap descriptions
We've fixed a bug where the Terraform exporter for escalation paths wasn't correctly setting a level's ack mode
Fixed a bug where we were showing the incorrect date range on pay calculator reports for some timezones
Fixed a bug where you couldn't configure a round robin cycle time in escalation paths when the level had a custom time to ack duration
Fixed a bug where we were incorrectly displaying the total on-call duration in the pay calculator for some users
Fixed a bug where we weren’t consistently grouping timeline items for notifications when there were multiple notifications associated with an escalation
Fixed a bug where we did not send cover request nudge notifications on MS Teams when falling back to DM when no mobile app was available
Fixed a bug where it wasn't clear that you didn't have permissions to delete a status page
Fixed a bug where we wouldn't show all the relevant users in a private incident unless you searched for them
Fixed a bug where we wouldn't respect the 'ranking' of components when using a ranked catalog type to power the components of a customer status page
Fixed a bug where you couldn't use the 'update status page' quick action button if you only have a customer status page
Fixed a bug with the timezone in the upcoming shift email notification being displayed wrong for some users
Fixed a bug where the delete team button on the team view page wasn't working
You can now mark paused incidents as related in Slack
We no longer let you try to add Scribe to calls if we can't access the right call information