Forms & Fields
Built-In Forms
Overview
Rootly comes with eight essential, built-in forms that cannot be deleted. The forms each cover a different stage of an incident and scheduled maintenance lifecycle. You can access the built-in forms by navigating to Configurations > Forms.
Form Types
New Incident Form
The New Incident form is displayed whenever the user first declares an incident on Slack (via/rootly new command) or on the Rootly web UI (via Create Incident button).
Update Incident Form
The Update Incident form is displayed whenever the user attempts to update an incident on Slack (via/rootly update command or Update button) or on the Rootly web UI (via Edit button).
Incident Mitigation Form
The Incident Mitigation form is displayed whenever the user attempts to mitigate an incident on Slack (via/rootly mitigate command) or on the Rootly web UI (via Mitigate button).
Incident Resolution Form
The Incident Resolution form is displayed whenever the user attempts to resolve an incident on Slack (via/rootly resolve command) or on the Rootly web UI (via Resolve button).
Incident Cancellation Form
The Incident Cancellation form is displayed whenever the user attempts to cancel an incident on Slack (via/rootly cancel command) or on the Rootly web UI (via Cancel button).
Incident Retrospective Form
The Incident Retrospective Form is displayed after the incident is resolved and the user enters the Gather & Confirm Data step of the retrospective. This form is only accessible from the Rootly web UI.
New Maintenance Incident Form
The New Maintenance Incident form is displayed whenever the user first declares a scheduled maintenance on Slack (via/rootly maintenance command) or on the Rootly web UI (via Schedule Maintenance button).
Update Maintenance Incident Form
The Update Maintenance Incident form is displayed whenever the user attempts to update a scheduled maintenance on Slack (via/rootly update command or Update button) or on the Rootly web UI (via Edit button).
You’ll notice that the trigger points for scheduled maintenance is exactly the same as for incidents. Rootly will be able to recognize the context and display the appropriate form. For example when
/rootly update is ran,- If it was ran in an incident channel, then Update Incident form will be displayed
- If it was ran in an maintenance channel, then the Update Maintenance Incident form will be displayed
Sub-Status Forms
If your Rootly instance has access to Rootly’s custom lifecycle feature, which allows you to customize your incident statuses, Rootly will generate default forms for each of your incident substatuses. This allows you to fully customize the information your responders provide throughout the incident’s lifecycle, attuned to your business processes. You’ll find these forms under the Sub-Status Forms tab.
Get started with Rootly’s custom lifecycle feature by reaching out to your account representative.
Edit Form
To begin editing a form, select the Configure button under the form you’d like to edit.
Select Display App
You can switch between Slack and Rootly web UI versions of the form by using the tabs at the top of the page.
Mark Field as Required
You can mark a field as required by hovering over the right hand side of the field name. An asterisk (*) will appear and if selected, will make the field a required field on that specific form.
Edit Field Position
You can rearrange the order of the fields by dragging them by the 6-dot area.
Remove Field
You can remove a field by clicking on the minus symbol. Removed fields will not appear on the selected form.
Add Field
You can add a new field by clicking on theAdd Field button at the bottom of the page.
Copy Fields From Slack/Web
You quickly match the Slack and Rootly web UI displays of the form by clicking theCopy fields from Web form or Copy fields from Slack buttons.
Preview
The preview is generated in real-time and it is interactive. This is a great way to test out the behavior of each field.