You can run workflows on private incidents

When it comes to private incidents, our top priority is keeping private incident data safe. Being able to harness the power of our whole product during a private incident is a close second.

It's now possible to build workflows that act on private incidents. We'll only let account owners make changes to these workflows, to make sure that other users can't use workflows as a way to gain access to sensitive information.

Along with that, we've also added a condition so you can choose to target only private incidents with your workflow (if you'd like).

You can learn more in our help centre.

What else we shipped

• 🆕 Web: You can now assign actions and follow-ups to a user (or role) when configuring workflows.
• 🆕 Web: You can specify the urgency when using a workflow to escalate to PagerDuty or OpsGenie.
• 💅 Web: You can search for users using their full names (not just their display names) in the web UI.
• 💅 Web: You can now choose shorter auto-archive windows.
• 💅 Web: Incidents with long names look better in the UI.
• 💅 Slack: It's now clearer that we won't announce test incidents anywhere.
• 💅 Slack: We've stopped tagging people in all our updates in Slack, so you can still see who did what, but without the unecessary noise.
• 👷 Web: Workflow dropdowns with lots of options are now much snappier.