Beautiful Incident Timeline Pages

πŸ“£ Beautiful Incident Timeline Pages

We are excited to release beautiful incident timeline pages that can be easily shared across the organization.

Why? Following along incidents can be noisy especially given the amount of collaboration required to debug the issue. Teams such as customer support are left wondering what is applicable to them and often causes confusion leading to more questions.

Incident timeline pages solve that by providing a high level overview of everything that is important that teams can easily follow along.

  • Updates to the incident timeline page are pinned automatically with πŸ“Œ emoji in Slack
  • Updates to timeline in the Web Platform automatically updates the incident timeline page
  • Link can be easily shared across the organization to Rootly users
  • Executive overview of all relevant information without scrolling around in Slack
  • Accessible links in both the incident channel overview in Slack and incident view on the Web Platform

🌝 New & Improved

  • πŸ†• Send Slack Message and Slack Blocks task in workflows now can be sent as ephemeral (Only you can view)
  • πŸ†• Adding responders via Opsgenie and VictorOps now split into users and teams instead of combined for easier search
  • πŸ†• Custom field support for Asana integration
  • πŸ†• Ability to configure assignee for Asana integration
  • πŸ†• Stepped line chart support in metrics
  • πŸ†• Stacked charts support in metrics
  • πŸ†• API support for CRUD custom dashboards in metrics
  • πŸ’… Reworked data model for integration that will unlock ability to leverage templates and components
  • πŸ’… PagerDuty integration better respects escalation policies and acknowledge events that is aligned with native PagerDuty
  • πŸ’… Infrastructure improvements to better support concurrent incident creation for a single organization
  • πŸ’… Action items in Web Platform grouped by their respective role, playbook, or other if applicable for easier categorization
  • πŸ’… PagerDuty and Opsgenie alerts are automatically closed when an incident is resolved
  • πŸ› Fixed issue where exporting metrics from specific charts as CSV and JSON did not work
  • πŸ› Fixed issue where elapsed time on Web Platform was not updating without a refresh
  • πŸ› Fixed issue in workflows if you set repeat every to 0 it causes an error

Manage Workflows via API, Terraform, and Pulumi

🧿 Manage Workflows via API, Terraform, & Pulumi

Rootly is the only enterprise-ready incident management platform that supports IaC via API, Terraform, and Pulumi.

Today, we are taking that one level further and enabling customers to manage workflows via API, Terraform, and Pulumi.

Workflows are at the heart of what makes Rootly able to be customized to encode each organizations individual incident processes.

Previously, managing these workflows (e.g. automatically create Jira ticket for on security board, invite infra team if SEV0, etc.) had to be done in our Web platform. This was manual and didn't align with how organizations were already leveraging IaC.

With the ability to now manage workflows through providers like Terraform, individual departments and teams can own workflow configuration without click-ops.


  • Docs with workflows support: here
  • Previous changelog release notes: here


  • Docs with workflows support: here
  • Previous changelog release notes: here


  • Docs with workflows support: here
  • Previous changelog release notes: here

🌝 New & Improved

  • πŸ†• Scheduled maintenance can be created from Slack using /incident maintenance, previously only available on Web platform
  • πŸ†• Assigning action items to others easier in Slack by right clicking and selecting πŸ‘‰ assign a user/team
  • πŸ’… Improvements to make tasks associated with playbooks more robust
  • πŸ’… General refactoring on our data model and configurations that improves overall loading and saving speeds
  • πŸ’… Adding action items on Web platform no longer require a refresh to populate
  • πŸ› Fixed issue where filters on alerts were not working for environments and services
  • πŸ› Fixed issue where export to CSV and JSON did not specify the title of the custom field
  • πŸ› Fixed issue where updating the organization page rendered a 500 despite data always being saved

Customizable Incident Metrics

πŸ“Š Customizable Incident Metrics

We are excited to launch the industries most powerful reliability and incident insights.

Previously, customers relied on a basic set of metrics that weren't editable. Now, customers can build beautiful custom dashboards and charts with data sliced the way they want. Think BI tools such as Tableau and Amplitude. Example use cases now enabled...

  • Postmortems that haven't been published and exceed SLA
  • High severity incidents with action items
  • Custom field for customer impact
  • Incidents with a Jira ticket and type was customer facing
  • ...endless possibilities in our simple to use query and chart builder

Custom Dashboards

For a variety of reasons such as by engineering team, executive reporting, or type of insights, a single dashboard is not enough to serve all use cases.

  • Create private dashboards only you can view (can be upgraded to public)
  • Create public dashboards shared with the organization and team
  • Drag and resize various charts on dashboard for a custom look and feel

Charts, Filters & Queries

  • Build custom charts with multiple filter groups for granular reporting
  • Leverage filters not only for incident metadata like severity but also integration attributes (e.g. Jira tickets, Datadog playbooks, Confluence pages)
  • Use custom fields (e.g. customer impact) as an attribute
  • Select from a variety of chart types (line, chart, bar, table, aggregate value, etc.)
  • Custom label chart title and axis

Reporting & Exports

Making data driven decisions around reliability and where to invest resources have never been easier. Customers can now present to stakeholders various views depending on the audience type and focus.

  • Executive summary (e.g. top line metrics and trends)
  • Beautiful reports with full-screen presentation mode
  • Audience specific reports

Keeping the garden walls low in Rootly is key priority as many will want to export incident data to existing BI or analytics tools. Export options include.

  • PNG, JPG
  • PDF

Out of The Box

Although advanced and customizable, metrics out of the box are ready-to-go to get started quickly. Key data around MTTX, incident count, severity, service impact, and more fetched automatically. All wrapped in a beautiful UX. Teams of all sizes can take advantage of this!

GA for all customers on Rootly Enterprise to try! πŸ₯³

🌝 New & Improved

  • πŸ†• Workflow task for Update Rootly Postmortem
  • πŸ†• API fields include Slack channels, aliases, and owners for services, functionalities, and teams
  • πŸ†• Workflow condition for any on top of all of, any of, and none of existing options
  • πŸ’… Better deduplication when importing PagerDuty teams to Rootly
  • πŸ’… Shiny new logos on
  • πŸ› Fixed issue where guidance when assigned a role wasn't formatted correctly

Microsoft Teams Integration

πŸ“Ή Microsoft Teams Integration

We are excited to announce our video conferencing integration with Microsoft Teams.

As we further our market leading position for enterprise readiness, organizations will now be able to collaborate over Teams for high bandwidth conversations as they tackle incidents.

  • Create a Teams bridge automatically whenever an incident starts
  • Automatically bookmark Teams bridge to incident channel for easy access
  • Edit/replace Teams bridge link (e.g. if an existing one is already in use)
  • Leverage workflows to dynamically create Teams bridge (e.g. only SEV0 and SEV1 require a call)

Our Teams integration sits alongside other video conferencing tools already supported such as Zoom, Google Meet, Slack Huddles, Webex, and more.

Docs for getting started:

🌝 New & Improved

  • πŸ†• Specify notification channel whenever a workflow fails to run, found in Profile > Organization Settings
  • πŸ†• Service dependencies inside of Rootly service catalog
  • πŸ†• Alerts (e.g. PagerDuty) that Rootly pipes into Slack can now be customized with specific messaging and CTA buttons (e.g. create incident, link to alert, etc.), found in Workflow > Alerts
  • πŸ†• Workflow triggers for custom fields (e.g. custom field updated, etc.)
  • πŸ†• Action items can be exported to PDF
  • πŸ†• Incident timestamps (acknowledged, detected, started, mitigated, resolved) can be used as a workflow condition (set or unset)
  • πŸ’… Paging responders in Slack modal now separates escalation policies and users instead of combining
  • πŸ’… UI polishes around workflows and tasks
  • πŸ’… Infrastructure enhancements that makes bulk emailing and inviting users to Rootly better
  • πŸ’… Migration from PagerDuty webhook v2 to v3, enables additional event types around signal changes to incident severity, responders, and all around better sync between the two
  • πŸ’… Alerts tab added to main navigation menu in Web platform and Pulses is now nested under configuration
  • πŸ› Fixed issue where some users were prompted to reintegrate PagerDuty
  • πŸ› Fixed issue where workflow conditions for action items could run into a race condition
  • πŸ› Fixed issue where elapsed time in Slack did not update
  • πŸ› Fixed issue where clicking on an related active incident in Web platform did not redirect you to active incident channel

Microsoft Azure Active Directory SSO Integration

πŸ”‘ Microsoft Azure AD (Active Directory) SSO Integration

We are excited to be featured in the official Microsoft Azure AD application marketplace!

The vast majority of our customers leverage SSO and Rootly already, the most popular being Okta, Google, and Azure AD.

With continued support for Azure AD, enterprises can securely manage access to Rootly seamlessly.

  • Control in Azure AD who has access to Rootly
  • Enable your users to be automatically signed-in to Rootly with their Azure AD accounts
  • Manage your accounts in one central location - the Azure portal
  • Take advantage of SCIM

Getting started with Rootly and Azure AD, written by Microsoft:

🌝 New & Improved

  • πŸ†• Shiny G2 badges for High Performer and Easiest To Do Business With for Summer 2022 on homepage πŸ₯³
  • πŸ†• Workflow task for updating an already created Google Calendar event (e.g. add more attendees programmatically to postmortem review meetings)
  • πŸ’… Google Calendar workflow task allows for modifying guest permissions (e.g. visibility of event, ability to invite others, ability to modify event)
  • πŸ’… Improved filter loading speed on Web platform
  • πŸ’… Improved filter UI with tasteful colours for easier navigation
  • πŸ’… More granular time settings for Google Calendar task (e.g. timezone support, wait time for skipping weekends)
  • πŸ’… Incident timeline loads 50 items instead of 10
  • πŸ’… 14-day free trial more accessible on homepage
  • πŸ› Fixed issue where emails after signing up for a trial were too noisy
  • πŸ› Fixed issue where there was a typo under incident type configuration
  • πŸ› Fixed issue where there was an UI bug for marking incidents as test on Web platform looked required

Backstage Integration

🏟️ Backstage Integration - Service Catalog

We are excited to announce our Backstage integration on the Backstage Plugin Marketplace.

Backstage is a popular service catalog tool open sourced by Spotify and is used by companies such as Netflix, DoorDash, Hello Fresh, and 100's of others including many of our customers.

We continue to reduce the fragmentation of tooling by building the most pluggable enterprise-ready incident management platform on the market.

Customers can substitute their Rootly service catalog with their existing Backstage implementation and seamlessly ensure both platforms remain in sync.


  • Easy to install by leveraging the official Rootly + Backstage plugin:
  • Import services created and managed in Backstage directly to Rootly
  • Create incidents in Rootly that pull from service impact directly from Backstage
  • Double click on services in Backstage and browse their respective incident history depending on what was impacted in Rootly
  • Browse incident metadata as granular as per service in Backstage such as severity, reporter, status, start/end time, etc.
  • Shortcut to create incidents in Rootly via Backstage for easy access
  • View on-going Rootly incidents in Backstage for broader visibility

In Action

Getting started guide:

🌝 New & Improved

  • πŸ†• Workflows for postmortem with status conditions (Draft, Published)
  • πŸ†• Incident variables for roles such as {{ incident.commander }}
  • πŸ†• Custom Fields now show up in Metrics
  • πŸ†• Option to cancel queued Workflows
  • πŸ†• Workflow task for Send Slack Message now includes the ability to add an action button for Esclating an incident
  • πŸ†• Versioning for Rootly postmortem templates
  • πŸ†• ServiceNow supports custom fields mapping of incident metadata
  • πŸ†• Workflow task for Sending Slack Message available under Action Item workflows
  • πŸ’… Ability to handle organizations with thousands of GitHub repositories for efficiently
  • πŸ’… Schedule Postmortem Meeting task can now exclude weekends
  • πŸ’… Workflow template for renaming a Slack Channel to a Jira ticket number
  • πŸ’… Ability to export metrics to PDF
  • πŸ’… PagerDuty and Opsgenie paging tasks in Workflows can now auto-match or select priority levels
  • πŸ’… Additional Workflow triggers such around creation and update of Postmortem and Causes
  • πŸ› Fixed issue where test/training incidents were appearing on the Rootly dashboard and summary emails
  • πŸ› Fixed issue on UI where pop-up modules rendered without the background

Linear Integration

🎟️ Linear Integration

It's no secret that Rootly has a powerful integration with Linear and is leveraged by customers already.

Today, we are formally launching in partnership with Linear on their integrations marketplace.

Customers will be able to automatically create and track tickets such as incident action items in Linear and ensure they bi-directionally sync. This can all be done from within Slack or Web.

  • Create a Linear issue when a new incident is created with relevant metadata
  • Create a Linear sub-issue when a new action item is created
  • Update an issue ticket to Done when an incident is resolved


  • Full customization and configuration via Workflows
  • Automate routing different Linear tickets to different boards depending on incident severity, type, team, or any other condition
  • Automatically sync incident severity with Linear priorities
  • Leverage incident variables to populate to customize ticket description, title, etc.

In Action

🌝 New & Improved

  • πŸ†• Add custom message when paging via Workflows to help provide more context, incident variables are also supported
  • πŸ†• Shortcut buttons pop up with common tasks in Rootly during long periods of inactivity to prompt if you need help, can be configured further in Workflows
  • πŸ†• Role-based incident variables (e.g. Send Slack message to Incident Commander)
  • πŸ†• Custom fields (e.g. customer impact) show up in Slack as part of the incident overview and is easily editable
  • πŸ’… Search and filtering capabilities to services and functionalities attribute in the Rootly API
  • πŸ’… Additional guidance for modifying custom wizard fields on Slack and Web
  • πŸ’… Action items view on Web by default exclude tasks and focuses on follow-up actions
  • πŸ’… UX improvements to incident summary in the Slack incident overview section to make it easier to digest
  • πŸ’… Error message when running a Slack command in an incident channel but that incident has been already deleted on Web
  • πŸ’… /incident help UX improvement to make finding and learning commands easier, does not require clicking into each one
  • πŸ› Fixed issue where date picker did not allow today to be set
  • πŸ› Fixed issue where assigning an action item to team did not immediately reflect in Slack
  • πŸ› Fixed issue where playbooks did not populate their respective checklist of tasks when incident was updated

Workflow Versioning

πŸ—„ Workflow Versioning

Introducing Workflow Versioning, a detailed audit trail and history of all changes made to a given Workflow.

Workflows are at the heart of Rootly. By making it easier to track changes made over time, teams will find Workflows even easier to manage and safely collaborate together than it already is.

Why? Previously, there was little to no visibility who made the change or what they were. Now there is a mechanism to quickly see what changes were made without needing to recall from memory and compare each Workflow attribute.

  • Visually pleasing so at a glance changes from one version to another are obvious (e.g. colour coding)
  • Version numbers and date changed
  • User that executed the change
  • The changes themselves track both past to present differences for all Workflow attributes (e.g. trigger, condition, task, etc.)

Existing customers can access this feature by heading into Rootly > Workflows > Clicking on any Workflow name > Versions.

🌝 New & Improved

  • πŸ†• Display in incident timeline all users that join the incident channel regardless if they're a Rootly user
  • πŸ†• Ability to filter by incident attributes in Rootly API
  • πŸ’… External postmortems on Confluence, Google Doc, Notion, and others display follow-up action items only, excluding tasks
  • πŸ’… Fresh coat of paint for with accessible links to G2 customer reviews
  • πŸ’… Naming for Rootly Incident Page is now aligned across both Web and Slack
  • πŸ’… Ability to delete Rootly generated postmortems
  • πŸ› Fixed issue where custom Workflow trigger commands in Slack weren't working
  • πŸ› Fixed issue where UI on Confluence and Google Doc postmortems had incorrect line spacing
  • πŸ› Fixed issue where occasionally private incidents were accessible via postmortem view
  • πŸ› Fixed issue where running /incident convert did not let you pin events to the incident timeline

Incident Feedback

✍️ Incident Feedback

Like organizations, your incident response process will evolve over time. We are making learning from incidents your superpower by closing the feedback loop.

Excited to announce the ability to collect incident feedback and data on the incident process. This will help reveal what is working and areas of improvement (e.g. communication).

Purposely designed to be accessible, feedback can be collected in Web or Slack, by default responders are automatically prompted when incident is mitigated/resolved or by running /incident feedback.


  • Fresh and accurate - gather feedback while still fresh and relevant instead of relying on postmortem review meetings a week late or manual surveys
  • Data - incidents scored on satisfaction and given an average ⭐ rating and text field for long form responses
  • Sample size - gather feedback from all incident responders and from those that would be less likely to voice their feedback for a holistic picture
  • Flexible - can use Workflows to modify feedback prompt timing and instructional text
  • Psychological safety - incident responders can submit feedback anonymously

🌝 New & Improved

  • πŸ†• Can define default roles for new users that join Rootly (e.g. Admin, Users, Observer, Commander, any custom created) in organization settings
  • πŸ†• Custom fields can be toggled on/off
  • πŸ†• Custom fields in Slack can be updated at any time and can be managed separately
  • πŸ†• Slack bots (including homegrown) other than Rootly can be automatically invited to incident channels just like responders
  • πŸ†• PagerDuty alerts Rootly pipes into Slack now include a link to PagerDuty for reference
  • πŸ†• Workflows can specify which days of the week to run (e.g. work days only M-F)
  • πŸ†• Workflow for updating Google Doc postmortem
  • πŸ’… API Reference revamp using Stoplight:
  • πŸ’… If pinning a Slack message to incident timeline fails, we provide a helpful error message
  • πŸ’… Loading speed improvements in Slack when drop-down lists are long
  • πŸ’… Notion task in Workflows now have the ability to select pre-canned postmortem templates in Rootly
  • πŸ’… Custom fields now display in Notion generated postmortems
  • πŸ’… Slack buttons in incident channels are shortened to reduce visual clutter
  • πŸ’… All new Rootly accounts by default post incident updates in threads instead of broadcasting to channel
  • πŸ’… Workflows are categorized by enabled and disabled
  • πŸ› Fixed issue where on rare occasions duplicate incidents were being created

Retroactively Create Incidents and Modify Timestamps

⏲️ Retroactively Create Incidents and Modify Timestamps

Declaring an incident the moment it actually starts may not always be possible. Sometimes we notice incidents hours or days later. This causes skewed timestamps that paint an inaccurate metrics picture.

We are announcing the ability to retroactively create incidents and modifying all timestamps (started, detected, acknowledged, mitigated, resolved).

Easily backfill past incidents and accurately reflect actual start and resolved times.

  • Available at incident creation on Web and Slack as "Change start time" field
  • User timezones displayed when selecting new date and time
  • Modifying timestamps available on Web (per incident) and Slack (/incident timestamp), accessible at anytime of the incident
  • Built in guardrails to prevent e.g. Resolved occurs before Started
  • Metrics automatically get updated

🌝 New & Improved

  • πŸ†• Export incident timeline to CSV, JSON, XML format (found at the bottom of your timeline)
  • πŸ†• Creating new incidents now showcase ongoing incidents to ensure duplicates are not created in both Web and Slack
  • πŸ’… Workflow task for Jira now supports Due date attribute
  • πŸ’… Infrastructure enhancements as our customer base continues to rapid grow
  • πŸ’… Placeholder text in Web provide better guidance when you haven't created your first incident or postmortem
  • πŸ’… Workflow task for Shortcut can now map to assignee
  • πŸ› Fixed issue where marking an action item as canceled in Slack did not accurately reflect the number of open items

Rootly helps you respond to incidents faster as a team and learn to prevent them in the future.