Required, Default, and Customizable Fields

🌾 Required, Default, and Customizable Fields

We are introducing Form Fields that will allow you to customize what you capture whenever an incident is created, updated, mitigated, and resolved.

Why? Incident response is unique across every organization and the data captured will vary dramatically. Where one organization may care about the incident type when the incident is resolved others may not. Customization is crucial to fit each organizations data models.

• Ability to mark fields as required for data compliance
• Ability to pre-populate default fields (e.g. severity is always triage until updated otherwise)
• Support across both Slack and Web Platform with independent control
• Reorder fields that reflect the how they show up in /incident new and in Web Platform

With the introduction of Form Fields, we’ve deprecated the need to separately manage Slack and Web Platform from separate locations and merged it in a single pane of glass.

This is now GA for all customers, try it here.

What else shipped

• 🆕 Ability to select PagerDuty or Opsgenie priority when paging
• 🆕 Workflow task for creating an Opsgenie alert
• 🆕 Custom fields support the ability to select default fields to pre-populate details
• 🆕 Ability to link Rootly services with Backstage via API
• 💅 Incident variable for {{ incident.jira_issue_key }} & {{ incident.linear_issue_key }}
• 💅 Infrastructure and CI improvements that allow our test suite to run 90% faster
• 🐛 Fixed issue where for few customers workflows ran despite wrong conditions
• 🐛 Fixed issue where using the incident variable quick selector pasted multiple values instead of one
• 🐛 Fixed issue where profile photos on incident timeline were incorrect

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