Multi-Organization and Workspace Support

🏘 Multi-Organization and Workspace Support

We are excited to launch the ability to have multiple organizations and workspaces of Rootly under the same roof and license.

Why? Companies and enterprises are not one dimensional in their needs. They are comprised of multiple departments, sibling organizations, acquisitions, and all of whom might have wide ranging requirements when it comes to how incidents are managed.

By having separate workspaces, organizations, and instances of Rootly, this unlocks the ability to not step on each others toes. For example, the NOC department will likely handle incidents differently from the rest of the company. The sister company that was acquired that will remain separate from the parent org has different tools they'd like to use. The SRE team that has a sandbox environment to experiment with new processes before rolling to production.

Use the same Slack workspace across all of your Rootly organizations! Upon incident creation, users will be asked to select which organization they would like to create their incident in (see header image).

Regardless of your organizational complexity, the UX for responders is simple and intuitive.

  • Be part of and switch between multiple organizations within the Web Platform without needing to logout
  • Support for multiple domains
  • Plug in the same or different integrations as needed (e.g. company uses the same Jira but different PagerDuty accounts)
  • User and usage is counted towards a single license

Existing users - to setup a new organization, contact your account team via Slack or Once enabled, on the Web Platform > Profile > Switch Organization. The ability to switch organizations on Slack will appear after you've integrated the same Slack workspace across multiple Rootly organizations automatically.

🌝 New & Improved

πŸ†• API endpoints to mark the incident as started, mitigated, resolved, and canceled
πŸ†• Default postmortem timeline is in chronological order and incident timeline is in reverse chronological order (most recent first)
πŸ’… Infrastructure improvements to how we handle webhooks
πŸ’… Significant infrastructure improvements around increasing test coverage
πŸ’… Incidents deleted by accident can be recovered by requesting to or in your teams shared Slack channel with Rootly
πŸ› Fixed issue where form fields where not being respected on the Web Platform when disabled
πŸ› Fixed issue where some Slack redirect links were incorrect


🎣 Webhooks

Rootly is the only enterprise-ready incident management solution. Part of that is extensibility of our systems. We are excited to kick-off 2023 by launching Webhook support.

Support for a variety of webhook events.

  • Incident lifecycle (e.g. started, resolved, deleted, etc.)
  • Postmortem (e.g. published)
  • Alerts
  • Workflows (e.g. started, completed, failed, etc.)

Additionally, detailed audit trail of when the webhook was delivered, if it's successful or not, and the request/response payload is made available.

Create unlimited number of webhooks with the ability to easily toggle on/off.

Available to all customers at time of publishing. Found in > Configuration > Webhooks.

Read more about this in our documentation.

🌝 New & Improved

πŸ†• Workflow trigger event for slack_channel_converted
πŸ†• API call for scheduled maintenance
πŸ†• Incident variable for converting incident timeline events into a table format
πŸ’… Incidents created from a PagerDuty alert will sync start time in Rootly with occurred at time in PagerDuty
πŸ’… PagerDuty and Opsgenie incidents created by Rootly escalations are marked as resolved whenever Rootly incidents are resolved
πŸ› Fixed issue where date picker on workflow triggers was not working
πŸ› Fixed issue where clicking change start time on Web Platform incident creation was not working
πŸ› Fixed issue where editing role permissions in RBAC was not working

Rootly Rewind 2022

βͺ Rootly Rewind 2022

We are excited to wrap up the year with Rootly Rewind 2022.

See how you performed by logging into Available to all customers starting today.

A few example statistics you can expect...

  • Incidents with the most responders
  • Estimated time saved from manual work
  • Months and days with the least incidents
  • Responders that were involved the most

Once you make it to the end a fun celebration awaits.

Thank you for tuning into our changelog this year. With your feedback, we've delivered hundreds of game-changing features and won many awards along the way.

Our team will be spending the rest of December laser focused on performance and reliability. Happy Holidays and see you in 2023!

🌝 New & Improved

πŸ†• Custom fields now support checkboxes
πŸ†• integration supports component groups in drop-downs
πŸ’… Uptime calculation updated for services and functionalities to align with industry standards
πŸ› Fixed issue where incident variable explorer was timing out
πŸ› Fixed issue where drop-down menus on Web Platform weren't loading for Firefox users
πŸ› Fixed issue where some conditions in workflows had a blank drop-down option

Trigger Workflow from Other Workflows

πŸ’« Trigger Workflow from Other Workflows

Workflows in Rootly can be triggered a number of ways. Manually, API, alerts, or based on specific conditions.

We are launching the ability to trigger workflows from other workflows. This provides granular control over exactly when specific workflows should run that may not be satisfied by our out of the box conditions.

This enables the ability to have nested workflows, create dependencies, and run a series of workflows all at once. The use cases are endless.

This can be found under Workflows > Tasks > Trigger Workflow.

🌝 New & Improved

πŸ†• Scheduled maintenance now supports custom fields
πŸ†• Auto-refresh option for metrics to continuously poll latest data, option to turn off as well
πŸ’… Users declaring an incident for the first time will be prompted an optional interactive tutorial
πŸ’… Increased API rate limits
πŸ’… /incident overview displays incident roles and assignee
πŸ› Fixed issue where team members page did not refresh upon search
πŸ› Fixed issue where Rootly status page SMS notifications were not firing

Send Threaded Slack Messages via Workflows

πŸͺ‘ Send Threaded Slack Messages via Workflows

Incident channels can quickly grow noisy with messages as you collaborate on resolving incidents.

To keep communications clean and focused, we are introducing the ability to send threaded Slack messages via workflows.

By being able to pick the visibility of how messages sent, less important ones such as simple updates do not need to be broadcasted to everyone.

Threaded messages can only be sent under original messages that Rootly had previously sent.

This can be configured in Workflows > Task > Send Slack Message or Send Slack Blocks.

🌝 New & Improved

πŸ†• Postman collection for Rootly API
πŸ†• Ability to trigger workflows via API
πŸ†• Ability to update custom fields on /incident update
πŸ’… Azure AD integration added to Rootly website
πŸ’… Enable and disable workflows colours are colourblind accessible
πŸ’… Incidents displayed on metrics are hyperlinked for easier navigation
πŸ’… Filter for incidents use and as a conditional and not or
πŸ› Fixed issue where naming of workflow conditions were inconsistent
πŸ› Fixed issue where metrics exports to PDF were formatted incorrectly
πŸ› Fixed issue where Incident Causes were not showing up on postmortem tab
πŸ› Fixed issue where unable to edit labels

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

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