Back to Changelog
Back to Changelog

November 30, 2021

Workflows

Workflows 2.0

Workflows 2.0

🔮 Workflows 2.0 - Next Gen Incident Automation

We are excited to introduce the next generation of our Workflows feature to help automate the entire incident process in a consistent way!

What has changed since Workflows 1.0? Well, now all integrations are supported by our simple but powerful automation engine!

  • Zoom / Google Meet
  • Confluence / Google Docs
  • PagerDuty / Opsgenie
  • Jira / Zendesk / Linear / Asana / Trello / Shortcut / ServiceNow / Airtable

Use cases with Workflows 2.0 that you couldn't before? A few examples:

  1. 🔮 Create Jira tickets on multiple project board depending on which team is impacted
  2. 🔮 Open a Zoom or Google Meet bridge for high severity (>SEV1) incidents for high bandwidth conversations
  3. 🔮 Automatically page the Infrastructure team via PagerDuty or Opsgenie whenever the postgres-db is impacted
  4. 🔮 Use different Confluence or Google Doc postmortem templates if the incident was security related
  5. 🔮 ...thousands of other combinations to fit your exact incident process!

We make getting started simple too. When you first configure an integration we'll automatically create the Workflow template for you in 1-click. You can go in and modify anything you want later.

Create Jira Task

We are excited to see what you come up with and build!


🌝 New & Improved

  • 🆕 Buyers guide for whether or not you should build or buy an incident management platform: https://rootly.com/buy-vs-build
  • 🆕 Add new item to incident timeline via /rootly timeline instead of only using an emoji 📌 to pin items
  • 🆕 More detail provided in Opsgenie alerts when paged via Rootly to give responders better context
  • 🆕 Significant loading and performance improvements on Web UI, especially noticable in incident creation
  • 💅 Delayed execution of Workflows now support less than 1 min time increments (e.g. wait 10 seconds)
  • 💅 Default Slack channel names use a sequential ID instead of UUID when there is a duplicate to keep name cleaner
  • 💅 UI improvement to show whenever a Workflow fails making it more obvious for users where to debug
  • 🐛 Fixed issue where modifying mitigate timestamp saved but did not refresh the UI
  • 🐛 Fixed issue where some Workflows occassionally double triggered
  • 🐛 Fixed issue where Linear priorities were not loading when configuring and mapping to Linear
  • 🐛 Fixed issue where Linear ticket generation did not show up in dedicated incident channel when created
Previous post
Previous post
You are viewing the latest post

Update Custom Incident Fields Using Workflows

🤖 Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

📊 Dashboard Sharing Permissions

✍️ Customize Your Wordbank for Automatic Incident Title Generation

🧠 Smart Defaults for Jira

🔌 The Rootly Plugin for Zendesk

🪄 Rootly Retrospectives

⚡ Command Palette: Lightning Fast Navigation with a Single Keyboard Command

Rootly Terraformer: Seamlessly Bring Workflows From Rootly’s UI to Terraform

Smart Defaults for Slack Configuration

Rootly Rewind: Celebrating 2023 With Our Amazing Customers!

Search and Filter Available Actions for Workflows

Incident Timeline Comments: Add Context and Move from Conversation to Action Seamlessly

Introducing: Rootly x ClickUp! Our New Integration for Seamless Collaboration and Task-Tracking

The New and Improved Home Dashboard

Guided Onboarding Flow for New Rootly Users

Fields List View and More UX Improvements for Forms & Form Fields

Bulk Actions for Incidents and Workflows

Share and Set Permissions for Rootly Metrics Dashboards

Bulk Edit Task and Follow-up Action Items

Create Fully Custom Slack Forms Using Our New Form Builder

Specify Public vs Internal Incident Titles on Your Rootly Status Pages

Integrate with Multiple Instances of Jira and Confluence

Auto map any user from PagerDuty and Jira to Rootly incidents with new user lookup