Bookmark Anything in Incident Slack Channel

๐Ÿ”– Bookmark Anything in Incident Slack Channel

We are introducing a new Workflow that allows you to bookmark any link, integration, or resource to the incident Slack channel.

Customers can now append the most critical information at the top of incident channels making it immediately accessible.

Built on top of our Workflows engine, not only are there powerful defaults out of the box but can be customized to suit any organization.

  • Have different bookmarks for different types of incidents (e.g. Security playbook vs. Infrastructure playbook)
  • Specify Title, Link, and Emoji
  • Out of the box incident dashboard and relevant integrations are bookmarked

So, what can you bookmark automatically? Pretty much anything, here are a few examples.

  • Integrations (e.g. Jira issues, Zoom rooms, Confluence postmortems, PagerDuty on-call schedule, etc.)
  • Internal resources (e.g. Datadog dashboards, etc.)
  • Playbooks / Runbooks (e.g. Restarting the database, Cloud provider outage, etc.)
  • ...endless possibilities!

๐ŸŒ New & Improved

  • ๐Ÿ†• The Rootly team will be at SREcon San Francisco from March 14-16 at Booth 111, come say ๐Ÿ‘‹
  • ๐Ÿ†• Condition in Workflows to specify Test / Training incidents that enable ability to build customized training
  • ๐Ÿ’… Canceled incidents do not show up on Dashboard anymore
  • ๐Ÿ’… Revamped /incident update modal
  • ๐Ÿ’… is more mobile responsive and friendly
  • ๐Ÿ› Fixed issue where Rootly status page updates were formatted incorrectly

Convert Existing Channels to Rootly Incidents

๐Ÿงž Convert Existing Channels to Rootly Incidents

Rootly provides the most comprehensive suite of onboarding tools to help companies rapidly adopt better incident management.

As with the introduction of any tool, you won't always remember to use Rootly for new incidents due to muscle memory.

For the times you forget, we are introducing /incident convert that allows you to turn existing incident channels into Rootly incidents.

  • Continue collaborating on incidents without losing context or stopping your conversation
  • Incident history preserved and no need to manually backfill into Rootly
  • Link to existing incidents if an on-going incident had already been created
  • Prompts to fill in incident details as if you were just creating a new incident (e.g. Severity)
  • Supports private incident channels

๐ŸŒ New & Improved

  • ๐Ÿ†• New coat on paint on with shiny new logos, testimonials, and product features
  • ๐Ÿ†• Reordering teams in Web reflect the order displayed in Slack create and update incident wizard
  • ๐Ÿ†• Ability to reorder components on Rootly status page
  • ๐Ÿ†• Ability to resend invites to Rootly with one click in Organization Members
  • ๐Ÿ†• New incident variable for {{ incident.roles }}
  • ๐Ÿ†• Integrations when incidents are created are shown as hyperlinks
  • ๐Ÿ’… Increased number of times we refresh and check for new Slack channels, reminder you can always go to Integration > Slack > Refresh Channels without waiting
  • ๐Ÿ’… Weekly summary emails are now sent Monday at noon instead of Friday end of day, enjoy your weekend!
  • ๐Ÿ’… Playbooks are displayed in two columns instead of one to reduce visual clutter
  • ๐Ÿ’… Continuing major refactoring internally to ensure Slack commands are even more resilient
  • ๐Ÿ’… Removed /incident connect step in /incident tutorial as all new users are automatically prompted to connect
  • ๐Ÿ› Fixed issue where removing labels from Jira did not save for some users
  • ๐Ÿ› Fixed issue where selecting State in Linear Workflow task did not populate results for some users
  • ๐Ÿ› Fixed issue where clicking save on Linear in Integration gave users an error page despite saving correctly
  • ๐Ÿ› Fixed issue where postmortem download to PDF was stalling
  • ๐Ÿ› Fixed issue where we displayed a duplicate Workflow task for inviting on-call users to Slack channels

Incident Preview

๐Ÿ” Incident Previews

The vast majority of customers have a global Slack #incident / #outages / #warroom channel.

This is where all incidents get posted for broader visibility.

At a quick glance, we are making it now even easier to know whether or not its important to various stakeholders.

  • Dynamic based on impact of incidents to avoid information overload (e.g. if no Service impacted then Service field won't display)
  • Shows any impact described at incident creation (e.g. SEV, Teams, Environments, etc.)
  • UI easily digestible to know if you should join the incident
  • Bold CTA guiding users to join incident channel if relevant

๐ŸŒ New & Improved

  • ๐Ÿ†• Ability to duplicate Workflows for faster repetitive automations
  • ๐Ÿ†• Custom date range filters instead of using defaults like Today, Last 7 Days, etc.
  • ๐Ÿ†• Updates to the incident (via /incident update) now get posted as a thread instead of new message in channel for easier access and to reduce noise
  • ๐Ÿ†• GCP added as 3rd party component in status pages
  • ๐Ÿ†• Assigning roles from PagerDuty on-call rotation supports override policies
  • ๐Ÿ†• Roles can now be assigned to the person creating the incident via Workflows
  • ๐Ÿ†• Workflow task to Update Incident (e.g. if incident updated to Security then update visibility to Private)
  • ๐Ÿ’… If GitHub integration returns zero commits we still let you know there is 0 commits
  • ๐Ÿ’… GitHub repos in timeline are now hyperlinked for easier access
  • ๐Ÿ’… After your account is connected with Slack we redirect you back to Rootly
  • ๐Ÿ’… Continued infrastructure enhancements to how we handle our Slack slash commands
  • ๐Ÿ› Fixed issue where emails Workflow did not respect defined formatting
  • ๐Ÿ› Fixed issue where Google Meet Workflow task had a typo

Custom Role-Based Access Control (RBAC)

๐Ÿ” Custom Role-Based Access Control (RBAC)

Rootly is already the most secure and enterprise-ready incident management platform on the market by a margin.

Today, we are taking that further by introducing role-based access control (RBAC) to our customers.

Why? Not all incident data or access is as simple as having Admin and User.

For example, create a Security role only for your InfoSec team or an Observer role for read-only access to give customer support.

  • Unlimited custom role creation with CRUD definitions
  • Granular permissions (e.g. configurations, incident data, Workflows, integrations, etc.)
  • Easily assign existing and new members new roles
  • Limit access to both Slack app (e.g. /incident new) and Web UI
  • Control who can access Private incidents (e.g. data breach)
  • Out of the box popular roles pre-defined and ready to use

๐ŸŒ New & Improved

  • ๐Ÿ†• Ability to edit timestamps of events added to the incident timeline
  • ๐Ÿ†• Send Slack message Workflow task supports pinging individual users instead of just channels
  • ๐Ÿ†• We want to encourage users to keep opening incidents, now they can be marked as Canceled
  • ๐Ÿ†• Workflow condition status for Canceled incidents
  • ๐Ÿ’… Made it easier to find the correct task type for Jira projects inside of Workflows
  • ๐Ÿ’… More descriptive error messaging at sign up for incorrect user actions
  • ๐Ÿ’… Infrastructure improvements on how we handle Slack commands internally, better reliability and performance
  • ๐Ÿ’… Welcome message to greet you when you log into Rootly on Web
  • ๐Ÿ’… Private incident alerts are always muted by default
  • ๐Ÿ› Fixed issue where all Asana projects did not load for larger organizations
  • ๐Ÿ› Fixed issue where invite to incident channel Workflow template had repeat and delay values set
  • ๐Ÿ› Fixed issue where deleting incidents in Web did not immediately get reflected in the UI

Subscribe to Incidents

๐Ÿ”” Subscribe to Incidents

We are introducing the ability to subscribe to incidents because staying in the loop is critical.

But different audiences want to be updated differently. A couple of examples.

  • Impacted Engineers - want to know every message sent because the details matter
  • Leadership - want to know when the incident is mitigated and resolved, exact details matter less

With the ability to subscribe to incidents, those that just want to follow along easily can do so.

  • Email notifications whenever the incident is Mitigated and Resolved
  • Anyone that enters the incident Slack channel automatically becomes a subscriber
  • Give your organization control to choose how they would like to be updated
  • Ability to subscribe or unsubscribe with a single click

๐ŸŒ New & Improved

  • ๐Ÿ†• Overview when incident Slack channel first created is automatically pinned for easier access
  • ๐Ÿ†• Ability to unpublish and edit already published postmortems inside of Rootly
  • ๐Ÿ†• Workflows run sequentially in 1-2-3 order instead of all at once
  • ๐Ÿ†• View in Linear button added next to any Action Items that are created
  • ๐Ÿ†• Linear integration in Workflows now support the ability to create incidents in a specific state (e.g. Todo)
  • ๐Ÿ’… Significantly reduced the number of clicks required to quickly edit configurations (e.g. Severity, Services, etc.) by redirecting users back to list view
  • ๐Ÿ’… New and standardized error pages for Web
  • ๐Ÿ’… UI improvements to postmortem tab in Rootly to make it clear when it's editable
  • ๐Ÿ’… New logos on Rootly homepage of customers we partner closely with, we'll periodically rotate them
  • ๐Ÿ’… New coat of paint for with a much more modern feel
  • ๐Ÿ’… Warning message indicating all other login methods will be disabled when SSO is enabled
  • ๐Ÿ› Fixed issue where hyperlink in Slack did not redirect you back to the status page after updating
  • ๐Ÿ› Fixed issue where images did not render properly inside of Rootly's native postmortem editor
  • ๐Ÿ› Fixed issue where searching for Jira project keys did not work inside of Workflows
  • ๐Ÿ› Fixed issue where search for Confluence space key did not work inside of Workflows

Workflow Templates

๐Ÿ“œ Workflow Templates

We are excited to introduce Workflow Templates to help you get started with Rootly even faster.

This is just one of the ways we continue to a) provide the most powerful defaults out of the box but b) still allow for flexibility and configurations.

Customers run hundreds of thousands of Workflows and we templated some of the most common ones:

  • Send update email
  • Reminder to update status page
  • Send generic reminder to incident channel
  • Invite users and teams to Slack
  • Send SMS and call
  • Auto-archive the incident
  • Auto-resolve the incident
  • Notify teams on Slack and summarize the incident
  • Page PagerDuty/Opsgenie responders

Many more to come!

๐ŸŒ New & Improved

  • ๐Ÿ†• Action items are now linked on postmortems written in Confluence and Google Docs
  • ๐Ÿ†• Slack notification to notify any incident subscribers whenever a postmortem is published
  • ๐Ÿ†• Workflow Task that allows auto-publishing events to your status page
  • ๐Ÿ’… Made UI changes to to make reading more pleasurable
  • ๐Ÿ’… Edits to that better highlight our strict compliance and security standards
  • ๐Ÿ› Fixed issue where CSV export did not respect pre-selected filters
  • ๐Ÿ› Fixed issue where creating Rootly status pages did not let you set it to public by default
  • ๐Ÿ› Fixed issue where some users were unable to mark incident action items as done in Slack
  • ๐Ÿ› Fixed typos in Incident Type
  • ๐Ÿ› Fixed issue where private incidents did not automatically prompt users to go edit postmortem

Incident Variables and Snippets

โœ‚๏ธ Incident Variables and Snippets

Incident variables such as {{ incident.severity }} are a way to quickly contextualize your communication without manual input.

We are excited to launch 100+ incident variables that span across Rootly and it's integrations (e.g. Jira, Google Doc, etc.).

They can be used in Workflows, incident title, postmortem templates, emails, and nearly everywhere in Rootly.

The use cases are endless, for example:

  • Summarize incident for leadership email {{ incident.summary }}
  • Rename Slack channel to align with Jira ticket number {{ incident.jira_issue_id }}
  • Indicate if incident Type is customer facing in postmortem title {{ incident.type }}
  • Send security team Slack message with incident channel link {{ incident.slack_channel_url }}

Incident variables and snippets are easily accessible via drop-down where available, no copy-paste required.

They are also dynamic in nature so you can set it and forget it.

๐ŸŒ New & Improved

  • ๐Ÿ†• Integrations such as Jira and Confluence links are now displayed at the top of incidents on Web for easier access
  • ๐Ÿ†• Mitigated and Resolved messages now get posted in incident channel, main incident notification channel, and in emails
  • ๐Ÿ†• Ability to search for organization members in
  • ๐Ÿ†• Total number of organizational members displayed now displayed
  • ๐Ÿ’… Invested in our backend infrastructure that makes editing content in Rootly snappier
  • ๐Ÿ’… Cleaned up native edit Postmortem UI
  • ๐Ÿ› Fixed issue where action items inside of Slack could not be marked as done
  • ๐Ÿ› Fixed issue where cookie consent over crowded the UI

Invite Responders to Incidents via Slack

๐Ÿ“ฎ Invite Responders to Incidents via Slack

Incidents are best tackled collaboratively and looping in the right responders fast is critical.

We've found today not only is it a manually intensive task but knowing who should be included is frustrating.

We are introducing a new Workflow Task to automatically add teammates into the incident Slack channel.

  • Supports both Slack users and Slack user groups (e.g. @oncall-infra, @legal)
  • Dynamically add people based on conditions set in Workflows (e.g. If postgres-db impacted then add Mary)
  • Users do not have to be signed up on Rootly in order to be added

๐ŸŒ New & Improved

  • ๐Ÿ†• New slash command for assigning roles via /incident assign or /rootly assign, eliminating the need to scroll up
  • ๐Ÿ†• Roles are exposed via the Rootly API
  • ๐Ÿ’… We simplified our syntax in URLs on Web
  • ๐Ÿ’… Made adding summary via /incident summary more obvious inside of incident channels
  • ๐Ÿ’… Continued to invest heavily in our own reliability and on-call structure, customers can page us if urgent
  • ๐Ÿ› Fixed typo in Slack integration
  • ๐Ÿ› Fixed issue where users weren't able to unassign from on-call roles

Severity Descriptions

๐Ÿฆท Severity Descriptions

What's the difference between a SEV0 and SEV1? Most organizations at best have this defined in an internal doc buried away.

However, that is not much use when you're under pressure and need to quickly create an incident.

We are introducing dynamic severity descriptions that change depending on what severity is picked to provide context.

  • Defined in Rootly > Configuration > Severities > Description
  • Dynamically changes depending on which severity level is picked
  • Reduce top of funnel friction during incident creation
  • Clearly and easily educate your organization on how to define severities

๐ŸŒ New & Improved

  • ๐Ÿ†• Action Items and Tasks have been merged into just Action Items. You can now decide if they are action items you do now (tasks) or do later (follow-ups).
  • ๐Ÿ†• Mitigated and resolved messages are displayed Slack incident channel for broader visibility
  • ๐Ÿ†• Integration with Dropbox Paper for postmortem
  • ๐Ÿ†• User settings are remembered if you toggle between grid or list view in Web UI
  • ๐Ÿ†• Markdown syntax support for severity description fields
  • ๐Ÿ†• Postmortems created in Google Docs can be written to shared Drive folders
  • ๐Ÿ’… Invested significantly into scaling our infrastructure and reliability as we continue rapidly onboard customers
  • ๐Ÿ’… Action items Web UI uses tags to indicate priorities instead of sections
  • ๐Ÿ’… Improved our SEO for better discoverability
  • ๐Ÿ’… Renamed Genius to Workflows for specific tasks that run in Slack (that should be them all, goodbye Genius!)
  • ๐Ÿ’… Added sign out link in Slack onboarding flow if users want to restart or use a different account
  • ๐Ÿ› Fixed issue where postmortem previews on Web UI dashboard looked incorrectly sized
  • ๐Ÿ› Fixed UI issue for connecting Slack accounts to Rootly

Reopening Incidents

๐Ÿฅก Reopening Incidents

We've all been there. Sometimes we get ahead of ourselves and close an incident too early before it's been resolved.

Today, we are excited to introduce the ability to reopen incidents and continue right where you left off without missing a beat.


  • Accessible in Slack via /incident status or /rootly status commands and in the Web UI (see above screenshot)
  • Metrics are updated accordingly to reflect the reopened incident to ensure accuracy
  • As always, you can go back and retroactively edit the state time of incident down to the minute
  • Ability to swap back and forth between all incident states (Started, Mitigated, and Resolved)

๐ŸŒ New & Improved

  • ๐Ÿ†• Pin to timeline feature now supports .docx format files
  • ๐Ÿ†• Rootly is now available for a 14-day trial with all enterprise features unlocked
  • ๐Ÿ†• Zoom meeting passwords are displayed in URL to make joining easier
  • ๐Ÿ†• We published our year in review for 2021 newsletter that recaps a few highlights
  • ๐Ÿ†• Ability to trigger manual Workflows at incident creation time
  • ๐Ÿ’… In Web UI we've made it more obvious when an incident is selected
  • ๐Ÿ’… Weekly summary email has been reformatted to be more spaced out
  • ๐Ÿ’… Improved loading of Opsgenie on-call schedules
  • ๐Ÿ› Fixed issue where deleting a Service required two clicks instead of one
  • ๐Ÿ› Fixed issue where occasionally unselecting severity in Web UI was stuck

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