Merge Duplicate Incidents

πŸ‘― Merge Duplicate Incidents

At Rootly, we advocate for everyone in the organization to be able to pull the fire alarm and declare incidents, not just engineers.

With everyone working concurrently and declaring incidents, its not uncommon to run into duplicate entries. Especially when the incident has a broad surface area of impact.

To help response teams reduce noise and effectively manage incidents, we are excited to introduce the ability to mark incidents as duplicates via the Web Platform or Slack (/incident duplicate).

Organizations no longer have to tiptoe around incident creation.

Marking duplicates during or after incident creation will also have downstream benefits - as the same issue will not be double-counted, resulting in more accurate metrics!

🌝 New & Improved

πŸ†• Introduced the ability to reference templates in workflow publish to status page tasks
πŸ’… Improved UX by pre-populating incident creation fields when incident is created from an alert
πŸ› Fixed Opsgenie escalation priority order
πŸ› Addressed issue with displaying incorrect resolution times in Slack
πŸ› Resolved inability to apply field positions in Terraform
πŸ› Corrected URL in private status page subscription email

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