Status pages API

We’ve just released a new API for Status pages, which allows you to programmatically update your status page so customers are aware of problems as soon as possible. Additionally, you can use the API to schedule routine maintenance windows in advance, push status updates and resolve incidents.

We’ve created a useful help document and you can review our API docs here.

Now in beta: Catalog graph!

We’ve built a visualization tool for Catalog, which can be tremendously helpful for when you want to view how different catalog entries connect to each other.

Additionally, you can easily take the URL of the graph view and share with others so you can both benefit from the same context.

Improved incident merging with @incident

We’ve shipped improvements when merging with the incident chatbot, making it smarter and more reliable. With this release:

@incident now searches for relevant incidents and surfaces recent ones as potential merge candidates
Merge detection has been improved so merges:
- Require less back-and-forth confirmation from the user
- Are better at identifying incident references (previously, you had to be very explicit)

What else we’ve shipped

New

You can now view the escalation timeline in the mobile app from the escalation details screen
We’ve introduced a new permission that allows a user to manage other users' on-call notification preferences
Alert messages are now posted to Slack with slightly longer attribute values; Max length has gone from 75 characters to 250 characters
We now support syncing multiple schedules to the same Slack user group
The "add member to incident" workflow step lets you automatically give people access to a private incident without a channel with a Workflow

Improvements

We'll now use the name of your alert source configuration for push notification titles
When restoring an old schedule version, we'll now show a preview of the current schedule compared with the selected version
When listing Slack channels we've made it clearer which ones belong to another workspace in your enterprise grid
We've improved how incidents are announced when paged via phone
In Slack and Microsoft Teams alert messages, we'll show more attributes if the space is available
We now tag Slack users when pinging them about debriefs

Bug fixes

We'll return an invalid value when you're unable to add new schedules via the API due to billing limits
Our new post-mortems now correctly tick the Export Post-Incident task when exported
We now return the required rotation layer name field when exporting Terraform code for schedules
Status icons now display correctly for cover requests in the mobile app
We fixed a bug where schedule overrides could not be created from the mobile app
We fixed a bug where attributes could not be created when creating a new alert source
Escalation timelines now correctly reflect when we sent users delayed notifications according to their notification rules
Fixed an edge case where re-opened Jira issues would leave follow-ups as closed when syncing
We've fixed sharing alerts from the mobile app, so that they can be opened directly in the app
We've fixed a bug where the On-call card was missing an upcoming shift when a user was on multiple schedules in an high urgency escalation path
We've fixed validation when editing workflow expression names
We've fixed a bug where you couldn't create multiple streams from a single workflow
We now show errors in the UI when creating an incident ticket in Jira Server fails due to incorrect permissions
We've fixed a bug where deactivating a SCIM user was not synced to the catalog correctly
Fixed broken scrolling on the incident sidebar
Respect post-incident flow conditions when creating a retrospective incident directly
Fixed policies not being re-evaluated in inactive incidents
Fixed our Terraform provider when updating an older workflow