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!

What else shipped

🆕 Introduced the ability to reference Statuspage.io 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

Editor’s note: Atlassian is retiring Opsgenie, with end-of-life scheduled for April 2027—factor a migration path into any evaluation.