Back to Changelog
Back to Changelog

August 25, 2022

Others

Incident Variable Explorer

Incident Variable Explorer

⛵ Incident Variable Explorer

Since our launch of incident variables (see changelog), they have quickly become an integral part of Rootly.

Customers leverage it today to build workflows, better automate communication, deep customization (e.g. rename incident title to Jira ticket number), and more. However, with 100s of options, knowing which ones to use and if they work can be confusing.

We are excited to launch our Incident Variable Explorer that makes as the name suggests browsing, exploring, and testing incident variables even easier.

  • Browse incident variable output on a per incident basis
  • Interactive incident variable preview to test and see example outputs based on incident selected
  • View all available incident variable options with context instead of scrolling through generic docs
  • Preview incident variable data for not only incidents but postmortems, action items, alerts, and pulses
  • View incident variable data for all integrations (e.g. {{ incident.jira_issue_url }})


🌝 New & Improved

  • 🆕 API endpoint for executing specific workflows
  • 🆕 Partial matching support for sources, labels, and payloads inside of workflows alerts and pulses
  • 🆕 Ability to define a name attribute in API key for easier identification
  • 🆕 Ability to sync Rootly incident title and events with PagerDuty incident title and status updates
  • 💅 Alert when /incident workflow example-command is ran outside of the automatically created incident channel
  • 💅 Additional education resources now live on Backstage Community repo
  • 💅 Ability to update custom fields in Update Incident workflow task
  • 💅 Freshly updated docs around our Statuspage.io integration
  • 💅 Additional incident variables for Google Meet
  • 🐛 Fixed issue where incident cause was not being attached to postmortems for some users
  • 🐛 Fixed issue where renaming workflow groups for alerts reset the incident kind
  • 🐛 Fixed issue where editing the incident channel Slack URL did not save
  • 🐛 Fixed issue where where filtering with JSON for events caused some webhook events to improperly filter
Previous post
Previous post
You are viewing the latest post

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

Customize Your Incident Overview Banner in Slack

Improved Confluence Retrospective Templates

Workflows Can Now Automatically Update Previously Posted Slack Messages

Automate Component Status Updates on Statuspage.io

Rootly Joins the Vendr+ Marketplace

Assign Multiple Users to the Same Incident Role

Incident Triage: Investigate Potential Incidents Faster

Rootly + Fivetran Data Connector Integration

Less Noise, More Flexibility: New Slack Notification & Emoji Options

SCIM Group Support: Access Control Made Easy at Enterprise Scale

Integrate With External Systems via HTTP Client

Custom Google Doc Permissions

Advanced Slack Customization via Slack Blocks

Notion Projects Integration with Rootly

WhatsApp Integration

Manually Export Action Items to Ticketing Apps (Jira, Zendesk, Linear, and more)

Automated Dashboard Reports