Autocomplete for Incident Variables

✏️ Autocomplete for Incident Variables

Incident variables has been one of the most popular ways to customize Rootly.

We've made this easier by introducing our Incident Variable Explorer earlier in the year. Now we are launching the ability to autocomplete incident variables as you type with inline suggestions.

With hundreds to pick from, browsing and selecting the right one has never been easier or faster.

🌝 New & Improved

πŸ†• Annotation support for Spotify Backstage integration
πŸ’… Terraform includes better deprecation messages
πŸ’… Action items in Slack are easier to assign to yourself
πŸ› Fixed issue where custom fields when disabled still appeared on incident mitigation in Slack
πŸ› Fixed issue where scheduled maintenance Slack channels displayed incorrect statuses instead of Scheduled, In Progress, Complete
πŸ› Fixed issue where scheduled maintenance status did not change in Slack
πŸ› Fixed issue where downloading Rootly postmortems gave users a 500 error
πŸ› Fixed issue where Slack Blocks task in workflows did not render drop-downs correctly

Playbook Tasks

πŸ“š Playbook Tasks

We are excited to launch Playbook Tasks, a checklist of pre-populated tasks whenever an incident starts that matches a specific criteria (e.g. security, high severity, etc.).

Consistency in incident response is everything. With playbook tasks, responders can work through a structured and interactive list of to-dos. Helpful for new responders who may not know the ropes, sensitive incidents that have regulatory requirements, and more.

  • Ability to pre-assign tasks or ad-hoc in both Slack and Web Platform
  • Lives alongside all other action items
  • Assign tasks to users or teams
  • Tasks can be enriched with markdown
  • Dynamically populates based on updates to the incident
  • Optionally track all tasks in Jira

Live today, customers can find it nested under Playbooks.

🌝 New & Improved

πŸ†• Date and time custom field option
πŸ†• Numbers custom field option
πŸ†• Multiple corporate domains can be associated to a single Rootly workspace
πŸ†• Workflow task for updating PagerDuty and Opsgenie incident
πŸ†• Support for PAT (personal access tokens) for Jira and Confluence on-premise
πŸ†• Ability to filter form and custom fields
πŸ’… Incident number added to incident list view on Web Platform
πŸ’… Opsgenie workflow templates for escalating incidents
πŸ’… Changelog now part of primary navigation for easier access
πŸ’… Backfilled incidents automatically get created in a resolved state
πŸ’… Incident timeline event colours coordinate with incident status
πŸ’… Incident timeline displays date and time together
πŸ’… Form field tags polished to be less noisy
πŸ’… Notifying main #incident channels has been migrated to workflows automatically
πŸ› Fixed issue where /incident integrations did not give the ability to edit Zoom links
πŸ› Fixed issue where unsubscribe from email notification settings were not saving
πŸ› Fixed issue where some drop-downs in Slack e.g. Services did not populate when clicked

Workflow Groups and Folders

πŸ—‚οΈ Workflow Groups and Folders

Workflows sits at the heart of Rootly and allow companies to encode and automate their own unique incident management process into the tool.

They can be created generically (e.g. creating incident channels, Zoom bridge), specific to teams, incident types, severity levels, integrations, and more.

With numerous workflows to manage, we are introducing a better way to organize them with workflow groups.

  • Easy drag and drop between groups
  • Supported via Terraform
  • Pre-created groups for default, tutorial, and disabled workflows

🌝 New & Improved

πŸ†• Rootly postmortems auto-save
πŸ’… Infrastructure improvements on Rootly status pages to be more resilient
πŸ’… Reworked a few confusing labels in workflow triggers to be more obvious what they do
πŸ› Fixed issue where playbook tasks weren't populating in Slack
πŸ› Fixed issue where related incidents were showing test incidents for some users
πŸ› Fixed issue where customer logo was not showing up on custom email branding
πŸ› Fixed issue where for some users said incidents had incorrectly elapsed one year

Optionally Create Incident Slack Channels

πŸ•ΉοΈ Optionally Create Incident Slack Channels

Do all incidents deserve their own Slack channel for collaboration?

Not necessarily. For example, incidents that have been previously resolved and are being backfilled, low severity incidents that don't require collaboration, etc.

Previously, all incidents required an incident Slack channel to be created. Today, creating incident channels has been migrated to workflows that enables granular control of when they should be created.

  • Set Slack workspace where the incident channel should be created
  • Set channel title with support for incident variables
  • Ability to set incident channel as private or public by default

🌝 New & Improved

  • πŸ†• Support for native Google Doc templates - see template example
  • πŸ’… Refreshed product images on
  • πŸ’… Link to incident dashboard from /incident overview
  • πŸ’… Tutorial for creating incident automatically from Jira and PagerDuty alerts
  • πŸ’… Cumulative charts hidden from metrics where it doesn't make sense
  • πŸ› Fixed issue where postmortems in Notion ran into workflow failures when incident timeline reached block limit

Backfill and Import Past Incidents

πŸ«— Backfill and Import Past Incidents

Inevitably there will be incidents captured outside of Rootly, for example, an outage that lasted a few minutes that was automatically resolved due to self-healing that was in place.

However, it is still important to track it for posterity. We are launching the ability to Backfill and Import past incidents.

  • Does not trigger workflows that normally would when incident is created
  • Reflected appropriately in metrics with modifiable timestamps for accuracy
  • Enable or disable ability to Backfill via Configuration > Form Fields
  • Supported via API

🌝 New & Improved

  • πŸ†• Live on Launch YC
  • πŸ†• Workflow trigger for Slack channel created
  • πŸ†• 6 min demo overview on Rootly
  • πŸ†• Workflow trigger and incident variable for whenever a new user joins the incident Slack channel, {{ trigger.user.slack_id }}
  • πŸ†• Ability to update role based tasks from Terraform
  • πŸ†• Ability to edit Slack Blocks from Terraform
  • πŸ†• Ability to edit action items from Terraform
  • πŸ†• Download metrics dashboard as PDF and email reports via workflows
  • πŸ’… Terraform errors surface exception message minimizing need to dive into logs
  • πŸ› Fixed issue where some PagerDuty accounts were failing to authenticate
  • πŸ› Fixed issue related to Terraform schema
  • πŸ› Fixed issue where Update PagerDuty Incident task would auto-populate title field
  • πŸ› Fixed issue where for some users they were listed as a subscriber of an incident twice
  • πŸ› Fixed issue where some workflows were running delayed
  • πŸ› Fixed issue where case insensitive slugs caused 500 errors
  • πŸ› Fixed issue where status page updates on Rootly were double posting
  • πŸ› Fixed issue where date picker was handling timezone incorrectly
  • πŸ› Fixed issue where workflow versions had empty changed by field for some users
  • πŸ› Fixed issue where most recent incident was listed second not first for some users on Web Platform

Customizable Interactive Tutorials

πŸŽ“ Customizable Interactive Tutorials

One of our largest investment areas is how we can help organizations drive better adoption of their incident management process.

We are excited to launch our Interactive Tutorials that are customizable and designed to effectively teach users about Rootly and your incident response process.

Why? It is unsustainable for individuals on an SRE team to teach everyone themselves. Current ways of learning via presentations, docs, and meetings are unmatched for hands on learning. Reduce on-call anxiety and improve muscle memory!

Launch your interactive tutorial via /incident test in Slack.

  • Default tutorial OOTB has turn-by-turn guidance and beautiful graphics for using Rootly
  • Easy to understand prompts that are interactive for completing a task
  • Customizable messaging and steps to suit your organization inside of workflows
  • Test incidents don't impact production metrics

🌝 New & Improved

  • πŸ†• Rootly is again awarded G2 Fall 2022 badges for High Performer, Easiest to Do Business With, and Users Love Us for Incident Management
  • πŸ†• Workflow task for adding a comment to Jira
  • πŸ’… Team members view defaults to 100
  • πŸ’… Continued infrastructure improvements specifically around our database
  • πŸ’… Icons for integrations inside of Slack got a fresh coat of paint
  • πŸ› Fixed issue around scheduled maintenance not notifying status page subscribers
  • πŸ› Fixed issue where deleting a workflow would redirect you incorrectly afterwards
  • πŸ› Fixed issue where incidents that were canceled still prompted users a banner that the incident was unresolved for 24hrs

Workflow Debugger

πŸ› Workflow Debugger

We are excited to launch our Debug Workflows capability for all customers!

If you've ever wondered why a workflow did not run and spent time debugging it, this is for you.

This compares incident conditions against expected values against actual values and provides a pass or fail result depending on what was satisfied.

  • Debug in seconds instead of manually cross checking if conditions were met
  • Drill down into specific workflows on a per incident basis
  • Used for incidents, postmortems, action items, pulse, and alert workflows
  • Support for custom field conditions

Our Workflow Debugger complements our other suite of engineering productivity tools such as Incident Variable Explorer.

🌝 New & Improved

  • πŸ†• Multi-select option on filters in Web Platform
  • πŸ†• Due date field for action items
  • πŸ†• Workflow task for adding comments to Linear tickets
  • πŸ†• Workflow task for updating Opsgenie alerts (acknowledge + close)
  • πŸ†• Incident variables for scheduled maintenance {{incident.scheduled_for}} and {{incident.scheduled_until}}
  • πŸ’… Better and human readable date filters for Rootly API
  • πŸ’… Cleaned up free trial demo data for action items
  • πŸ’… Less noisy default Form Fields on free trials
  • πŸ’… Better error messaging when free trial has ended
  • πŸ’… Removed deleted workflows from showing up in Debug Workflows
  • πŸ’… Removed confusing drop down menus from incident creation on Web Platform
  • πŸ’… Default 90 day filter for metrics
  • πŸ’… Updated customer logos on Rootly
  • πŸ› Fixed issue where canceling the creation of a workflow via template gave a 404 error
  • πŸ› Fixed issue where some redirect links for integrations gave a 500 error
  • πŸ› Fixed issue where services and teams updated trigger were not firing properly

Required, Default, and Customizable Fields

🌾 Required, Default, and Customizable Fields

We are introducing Form Fields that will allow you to customize what you capture whenever an incident is created, updated, mitigated, and resolved.

Why? Incident response is unique across every organization and the data captured will vary dramatically. Where one organization may care about the incident type when the incident is resolved others may not. Customization is crucial to fit each organizations data models.

  • Ability to mark fields as required for data compliance
  • Ability to pre-populate default fields (e.g. severity is always triage until updated otherwise)
  • Support across both Slack and Web Platform with independent control
  • Reorder fields that reflect the how they show up in /incident new and in Web Platform

With the introduction of Form Fields, we've deprecated the need to separately manage Slack and Web Platform from separate locations and merged it in a single pane of glass.

This is now GA for all customers, try it here.

🌝 New & Improved

  • πŸ†• Ability to select PagerDuty or Opsgenie priority when paging
  • πŸ†• Workflow task for creating an Opsgenie alert
  • πŸ†• Custom fields support the ability to select default fields to pre-populate details
  • πŸ†• Ability to link Rootly services with Backstage via API
  • πŸ’… Incident variable for {{ incident.jira_issue_key }} & {{ incident.linear_issue_key }}
  • πŸ’… Infrastructure and CI improvements that allow our test suite to run 90% faster
  • πŸ› Fixed issue where for few customers workflows ran despite wrong conditions
  • πŸ› Fixed issue where using the incident variable quick selector pasted multiple values instead of one
  • πŸ› Fixed issue where profile photos on incident timeline were incorrect

Zapier Integration

⚑ Zapier Integration

Rootly boasts the most extensible incident management platform with the most comprehensive 3rd party integration library, Open API, and capability to make external API via workflows.

Today, we are excited to announce our integration with Zapier (5000+ no-code integrations), taking our pluggable ecosystem one step further. A few things you can do.

  • Create incidents from emails that have incident in the subject line
  • Update customer in Salesforce when a new incident is created
  • Intercom conversations tagged with #incident send alerts to Rootly
  • Alerts from Pingdom automatically create incidents in Rootly

Zapier supports triggers for Incidents, Alerts, and Pulses (e.g. deploy changes).

Getting started documentation:

🌝 New & Improved

  • πŸ†• Awarded Users Love Us badge by G2 for consistently high customer satisfaction
  • πŸ†• Ability to configure separate emojis for follow-up action items πŸ“ (do later) and task action items ⭐ (do now)
  • πŸ†• Official plugin support for Roadie, a managed Spotify Backstage platform
  • πŸ†• Template support for Rootly status pages (not
  • πŸ†• Ability to reorder columns by clicking on headings for Incident and Postmortem in table view
  • πŸ†• LinkedIn product page for Rootly
  • πŸ’… Infrastructure improvements for workflow execution and accuracy
  • πŸ’… Deprecated birds eye view from incidents and postmortem on Web Platform
  • πŸ’… /incident support allows for questions as a request type, previously only allowed bug reports or feature requests
  • πŸ’… Verbiage changes around consistently calling licensed Rootly users organizational members in the Web Platform
  • πŸ’… Verbiage changes around how Private Incidents to better align with RBAC capabilities
  • πŸ’… Better mobile web support for
  • πŸ› Fixed issue where topic updates in incident channel were double and triple posting
  • πŸ› Fixed issue where user profile photos in the incident timeline were inaccurate
  • πŸ› Fixed issue where schedule maintenance was not triggering correctly

Scheduled Maintenance

πŸ”§ Scheduled Maintenance

Rootly serves as a single pane of glass for incidents and now scheduled maintenance events.

A scheduled maintenance is a period of planned downtime communicated in advance. Like incidents, they share many of the same fields such as title, summary, service impact, and more.

Customers can create a scheduled maintenance event directly from Slack or Web Platform.

Maintenance specific workflows around communication, escalation, and more can be built separate from typical incident workflows.

  • Schedule start and end time for scheduled maintenance
  • Upgrade a scheduled maintenance to a full incident if necessary (e.g. create incident channel)
  • Ability to update status page of scheduled maintenance
  • Select impacted services, functionalities, teams, and more
  • Maintenances displayed in Rootly are visually different from incidents and by default created silently

🌝 New & Improved

  • πŸ†• Incident variable for {{ incident.action_items }}
  • πŸ†• Shortcut button for adding action items after an incident is resolved in Slack
  • πŸ†• Terraform support for custom fields in workflow triggers
  • πŸ’… Attaching Rootly services and functionalities hidden when configuring Atlassian Statuspage
  • πŸ› Fixed issue where postmortems still persisted on Rootly dashboard after incident was deleted
  • πŸ› Fixed issue where elapsed time on Web Platform was not dynamically refreshing

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