Back to Changelog
Back to Changelog

August 15, 2024

Integrations

🧼 Redesigned Incident Announcement & Update Slack Blocks

🧼 Redesigned Incident Announcement & Update Slack Blocks

Rootly users can set a default Slack channel where new incidents are announced whenever they’re created. This helps increase visibility for new and ongoing incidents across your organization, while keeping the actual incident channel dedicated to those directly involved in the response. This channel can be updated from the Slack Configuration page:

We’ve given these announcements a makeover to show more information in a beautiful, easy-to-read display in Slack. As a refresher, here's what the announcements looked like before this update:

The original Incident Announcement block design included the incident's creator and title.

Users could then click the incident channel linked to discover more information like the incident’s status and summary. 

Now, we’ve redesigned these announcement blocks with more information and visual cues so it’s easier than ever for users to get a high-level overview of the incident without clicking into the channel. Here's how they look now!

The new Incident Announcement Slack block design!

These blocks automatically update as the incident progresses so you never have to worry about confusion due to out-of-date information. This means:

  • The summary shown in the announcement block will always be the latest summary.
  • The status indicator emoji will update whenever the incident moves to a new status (🔴 Started, 🟠 Mitigated, 🟢 Resolved,  🔀 In triage).
  • When the status or severity of an incident are updated, the previous state will be shown in strikethrough text (e.g. Started → Mitigated) for clear change tracking.

You’ll also be able to see newly redesigned Incident Update blocks in the thread from the original Incident Announcement block whenever these key details (summary, status, severity) are updated:

To see more of what Rootly can do in Slack, check out your (also newly redesigned) Slack Configuration in Rootly web (Home > Configuration > Slack).

🌝 New & Improved

🆕 Smart Default settings enabled for Google Meet and Zoom integrations. Teams no longer have to build workflows to create meeting bridges. Now, it can all be done through each of the two application’s integration pages.

💅 Updated scrolling behavior on On-Call Schedules page to ensure search bar is always in frame, regardless of how far down the page the user scrolls.

💅 Improved display of alerts on /rootly add alerts Slack modal

💅 Re-tuned backend processing logic to ensure better reliability when declaring incidents via Slack

🐛 Fixed inability to update timestamps on schedule maintenances through Slack.

🐛 Added back missing link to view list of outgoing webhook deliveries

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