๎‚ Back to Changelog
๎‚ Back to Changelog

June 6, 2024

Others

๐Ÿช„ Dynamic Forms

๐Ÿช„ Dynamic Forms

Rootly comes pre-configured with a set of Default Forms used to collect key information to help you track incident data at the time of incident creation, resolution, and more. You can customize these forms by adding or changing the custom fields within them, or create your own forms from scratch. Fields refer to the individual sections within each form โ€” Rootly also provides a large selection of fields to choose from and the ability to create your own.

Now, weโ€™ve introduced even more flexibility into forms with the ability to create Dynamic Forms! Dynamic Forms allow you to configure separate versions of your forms that apply under certain conditionsโ€”for example, a specific incident type. If none of your conditions apply, the default version of the form will be used.

Some benefits of using Dynamic Forms:

  • Only collect the data that matters for each specific incident
  • You can reduce the amount of form fields to make data collection more efficientย 
  • Set clearer parameters among teams for which fields are optional or requiredย 
  • More control for teams to choose the data they want to collect

In this demo, Ashley walks you through a quick use case creating a dynamic incident creation form for security incidents:

Learn more about Dynamic forms in our Help Docs.

Ready to start using Dynamic Forms? Reach out to Rootlyย Support today to request enablement of this feature!ย 

๐ŸŒ New & Improved

๐Ÿ†• Sub-incidents can now be referenced through the {{ incident.sub_incidents }} liquid variable from the parent incident. Teams can now configure workflows to update or send messages to the child incident(s) when the parent incident status changes.

๐Ÿ†• Multiple alerts can now be systematically attached to an incident via Alert Workflows.

๐Ÿ’… Bulk editing capabilities are now available on the Alerts page of the Rootly web dashboard.

๐Ÿ’… Resolution and mitigation messages are now configurable fields that can be included built-in and custom forms.

๐Ÿ› Fixed intermittent issue with teams unable to receive Slack messages when multiple team channels are targeted in the Send Slack Message and Send Slack Block workflow actions.

๐Ÿ› Fixed issue with non-users being able to be added to Rootly On-Call rotations.

โ€

๎‚ Previous post
๎‚ Previous post
You are viewing the latestย post

๐Ÿ‘ฏโ€โ™€๏ธ On-Call Shadowing

๐Ÿ”Œ Generic Webhook Alert Source

๐Ÿ”’ Lock Individual Workflows

๐Ÿฆโ€โฌ› Round Robin Escalation Policies

๐Ÿšจ Alert Sources

๐Ÿ”” Configurable On-Call Shift Reminders

๐Ÿช„ Dynamic Forms

๐Ÿ” Granular Role-Based Access Control Settings for On-Call

โœ‰๏ธ Emails as an On-Call Alert Source

๐Ÿ—“๏ธ View Multiple On-Call Schedules Together

๐Ÿค Partial Shift Overrides in Rootly On-Call

๐Ÿ—๏ธ Terraform + API Support for Rootly On-Call

๐Ÿฆ‰ Rootly x Thena Integration

๐ŸŽฌ New Full Platform Tour on Rootly.com

๐Ÿ”ฆ Drop-down Search in Escalation Policy Builder

๐ŸฆŠ GitLab Integration

Update Custom Incident Fields Using Workflows

๐Ÿค– Ask Rootly AI (+ More New AI Features!)

Rootly AI Editor: Fix Typos, Grammatical Errors, and Wordy Text Instantly

๐Ÿ“Š Dashboard Sharing Permissions

โœ๏ธ Customize Your Wordbank for Automatic Incident Title Generation

๐Ÿง  Smart Defaults for Jira

๐Ÿ”Œ The Rootly Plugin for Zendesk

๐Ÿช„ Rootly Retrospectives

โšก Command Palette: Lightning Fast Navigation with a Single Keyboard Command