Get Rootly's Incident Communications Playbook

Don't let an incident catch you off guard - download our new Incident Comms Playbook for effective incident comms strategies!

By submitting this form, you agree to the Privacy Policy and Terms of Use and agree to sharing your information with Rootly and Google.

Back to Changelog
Back to Changelog

January 17, 2025

Integrations

🔀 Integrate with Linear Triage

🔀 Integrate with Linear Triage

Tasks and follow-ups are constantly created as part of an organization’s incident management process: whether it’s a follow-up task to complete after an incident, or an urgent escalation from a stakeholder that needs to be investigated right away.

With Rootly On-Call and Linear Triage, say goodbye to un-groomed backlogs, unanswered pages, and missed escalations. New tickets added to your Linear Triage queue will be automatically assigned to your current on-call team member, allowing them to be the point person for all urgent matters for your teams, products, and services.

This ensures that urgent issues are quickly identified, investigated, and escalated. Your team can acknowledge and resolve problems faster, leading to improved product quality and a better overall customer experience.

Get started with Rootly and Linear

To begin using your Rootly On-Call schedule in your Linear teams, follow this guide to integrate your two systems. Next:

  1. Edit the Rootly schedule that you’d like to sync with Linear. Navigate to ‘Integrations’ and toggle on the ‘Sync with Linear’ setting.
  2. In Linear, edit your desired Team’s Triage settings.
  3. Click ‘Use schedule’ under Triage Responsibility, then select your Rootly schedule’s name.

Once configured, all new triage tickets will be automatically assigned to your on-call responder!

🌝 New & Improved

🆕 Added API and Terraform support for managing Alert Sources.

🆕 Added Global Alert Grouping to help teams consolidate related alerts, reduce noise, and focus on identifying and resolving the root cause.

💅 Enhanced alert workflows capabilities with Alert Status Updated triggers and Alert Status run conditions.

💅 Enhanced mobile API around user details, schedules and calendar view

💅 Improved ease of use on UI for copying IDs throughout the system

🐛 Fixed issue with Terraform that was blocking dynamic escalation paths from being created

🐛 Fixed status page latency issues

🐛 Fixed timeout issue when updating SCIM groups

Previous post
Previous post
You are viewing the latest post

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

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