Incident Variables and Snippets

βœ‚οΈ Incident Variables and Snippets

Incident variables such as {{ incident.severity }} are a way to quickly contextualize your communication without manual input.

We are excited to launch 100+ incident variables that span across Rootly and it's integrations (e.g. Jira, Google Doc, etc.).

They can be used in Workflows, incident title, postmortem templates, emails, and nearly everywhere in Rootly.

The use cases are endless, for example:

  • Summarize incident for leadership email {{ incident.summary }}
  • Rename Slack channel to align with Jira ticket number {{ incident.jira_issue_id }}
  • Indicate if incident Type is customer facing in postmortem title {{ incident.type }}
  • Send security team Slack message with incident channel link {{ incident.slack_channel_url }}

Incident variables and snippets are easily accessible via drop-down where available, no copy-paste required.

They are also dynamic in nature so you can set it and forget it.


🌝 New & Improved

  • πŸ†• Integrations such as Jira and Confluence links are now displayed at the top of incidents on Web for easier access
  • πŸ†• Mitigated and Resolved messages now get posted in incident channel, main incident notification channel, and in emails
  • πŸ†• Ability to search for organization members in https://rootly.com/account/memberships
  • πŸ†• Total number of organizational members displayed now displayed
  • πŸ’… Invested in our backend infrastructure that makes editing content in Rootly snappier
  • πŸ’… Cleaned up native edit Postmortem UI
  • πŸ› Fixed issue where action items inside of Slack could not be marked as done
  • πŸ› Fixed issue where cookie consent over crowded the UI


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