Rootly carefully selected the built-in properties based on common attributes used to characterize incidents. However, not all organizations are built the same and sometimes the built-in properties are not enough to meet everyone's requirements.

To enable a fully bespoke experience, Rootly introduced custom properties that can be set up to meet the exact specifications of your organization's incident management requirements.

Select the Create New Form Field button to begin creating a new custom field.

Fill in the following fields and select the Add button to add your custom field.

This is the general field type, which can only be Custom Field.

The value entered here will be the value that appears on user-facing forms.

This value WILL dictate how the custom field is referenced in Liquid syntax. This is because the syntax used to reference a custom field uses the slug value, which is the name lower-cased and hyphenated.

This field allows you to select the field type, which will dictate how the user interacts with this field. For example, a checkbox type will be a boolean field while a select type will ask the user to select one out of many options.

For more details on the available field types, please scroll down to the Supported Field Types section.

This field allows you to select the value type for select and multiple select fields. The following Value types are available: custom text options, teams, services or users.

For example, an organization may want to identify both an 'Owning Team' as well as a set of 'Impacted Teams.' A new custom field could be created for 'Impacted Teams' and the existing 'Teams' field could be renamed to 'Owning Team.'

Custom fields can be configured to have a default value. For example, if you want all your incidents to default to Unknown for the Root Cause custom field, then you can set it here.

Only enabled fields are considered to be live fields - meaning they can appear on UI screens and be updated during incidents. Disabled fields are NOT usable during incidents and cannot be updated by workflows either.

This switch allows you to display or hide the specific field on the Details section of the Incident Details page.

Only enabled fields are considered to be live fields - meaning they can appear on UI screens and be updated during incidents. Disabled fields are NOT usable during incidents and cannot be updated by workflows either.

You can use the toggle switch next to the field name to enable/disable it.

You can edit a specific field by clicking on the edit icon on the right hand side of the field.

Once selected, you will see an Edit Form Field pane open. From here, you'll be able to edit the attributes of this particular field.

This is an unique identifier for the form field. It is automatically generated for you upon field creation and cannot be edited. This id will be used to reference the specific form field in API calls and Liquid syntaxes.

This field can be edited. The value entered here will be the value that appears on user-facing forms.

Unlike built-in fields, changing the name of a custom field WILL alter the Liquid syntax used to reference it. This is because the syntax used to reference a custom field uses the slug value, which is the name lower-cased and hyphenated.

This field can be used to display a description for the custom field. This is particularly helpful if you want to give your users some instruction on how to fill in the custom field.

This field allows you to select the field type, which will dictate how the user interacts with this field. For example, a checkbox type will be a boolean field while a select type will ask the user to select one out of many options.

For more details on the available field types, please scroll down to the Supported Field Types section.

This field allows you to define selectable options for Select and Multiple Select field types when the 'Custom text' field value is selected.

Custom fields can be configured to have a default value. For example, if you want all your incidents to default to Zone 1 for the Zone custom field, then you can set it here.

Only enabled fields are considered to be live fields - meaning they can appear on UI screens and be updated during incidents. Disabled fields are NOT usable during incidents and cannot be updated by workflows either.

You can use the toggle switch next to the field name to enable/disable it.

This switch allows you to display or hide the specific field on the Details section of the Incident Details page.

Custom fields can be deleted by clicking the trash symbol.



Rootly supports various field types. Each field tyle has their intended use case and Liquid syntax. Below sections goes in more depth on each field type.

Custom fields can be referenced either by the field id or slug.

A text field is used to input single-lined free-form texts, such as names or addresses.

The following Liquid syntax will allow you to reference a custom text field:

A textarea field is used to input multi-lined free-form text, such details or comments.

The following Liquid syntax will allow you to reference a custom textarea field:

A select field is used to select a single value from a list of predefined values.

The following Value types are available:

The following Liquid syntax will allow you to reference a custom select field:

A multiple select field is used to select one or more values from a list of predefined values.

The following Value types are available:

The following Liquid syntax will allow you to reference a custom multiple select field:

A date field is used to select a specific date. Rootly uses a calendar style date picker on the UI.

The following Liquid syntax will allow you to reference a custom date field:

A datetime field is used to select a date and a time. Rootly uses a calendar style date picker and HH:MM AM/PM styled time picker on the UI.

The following Liquid syntax will allow you to reference a custom datetime field:

A users field is used to select one or more users from the list of users in your organization's Memberships page.

The following Liquid syntax will allow you to reference a custom datetime field:

A number field is used to input a numeric value. Rootly enforces that only numeric values can be entered into this field type.

The following Liquid syntax will allow you to reference a custom number field:

A checkbox field is used to select true or false.

The following Liquid syntax will allow you to reference a custom checkbox field:

If you need help or more information about this integration, please contact [email protected] or start a chat by navigating to Help > Chat with Us.