Custom Fields

🌿 Custom Fields

The most configurable incident management platform just got even more flexible!

We are announcing the ability to define custom fields anywhere in Rootly to ensure unique incident data can be captured, even if they're customer specific.

Endless use cases

• Which customers have been impacted?
• How the incident was detected?
• Revenue impact?
• What geographies were impacted?
• Were the right responders part of the incident?
• etc...

Customizable for any use case

• Supports both Slack + Web platform and can be separately configured
• Determine where custom fields should be captured: incident creation, mitigation, resolution, or postmortem
• Pick between single select, multi-select, and free text custom field types (more coming soon!)
• Set the fields as either optional or required

Are Workflows supported?

Yes! Any custom field defined will show up as a new condition inside of Workflows. That means you can run Workflows based on custom field inputs (e.g. emailing a specific customer when they are impacted).

Existing customers can try it today by visiting Configuration > Custom Fields.

🌝 New & Improved

• 🆕 Trigger in Workflows for when roles (e.g. commander, scribe, etc) are assigned
• 🆕 Ability to update Rootly generated integration links via /incident integrations command (e.g. replace Zoom bridge with existing one)
• 🆕 See why our customers rated us ⭐⭐⭐⭐⭐ on G2!
• 🆕 Import PagerDuty services to Rootly functionalities
• 🆕 Incident updates (Mitigated, Resolved) in main incident announcement (#incident, #warroom) channel have the option to be threaded
• 💅 Owner has been renamed to Reporter to bring greater clarity who created the incident
• 💅 Incident variable {{ incident.subscribers | map :email }} to invite any participant in the incident to postmortem review meeting
• 💅 Running /incident help brings up all Rootly commands faster
• 💅 Better support for PagerDuty escalation policy when auto assigning roles
• 💅 Descriptions for roles support markup and links by default
• 🐛 Fixed issue where modifying incident timestamps weren't saving
• 🐛 Fixed issue where users without permission to invite teammates still saw the option (although it didn't work for them)