Incident summaries are not only a great way for responders to gain context on an issue but are also an important way for observers to follow along with what’s happening.
Previously, internal status pages only showed the most recent update—these "in-the-moment" updates can often be technical, and don’t necessarily provide the broader context of the incident.
Now, internal status pages can be configured to also display the incident summary. This provides a quick and easy way for observers to stay informed with a concise and easily readable overview.
If you’re a user of Asana, ClickUp, or GitLab, you can wave goodbye to manually exporting your follow-ups.
You can now automatically export your follow-ups to your favorite issue tracker, making sure all your follow-ups end up in the right place.
Get started with our guide.
In addition to supporting incident tickets in Jira, we now support incident tickets in both GitHub and GitLab ensuring everyone can stay up-to-date as your incidents progress.
Head over to Settings → Incident tickets, set up export templates for your GitHub or GitLab projects, and decide which incidents should use each template. We'll handle the rest, keeping your tickets updated and posting incident updates as comments.
policy_user_labels
in the payload