Skip to main content
A field rule runs a workflow when a ticket’s custom fields change and the new values match the conditions you set. For example, run a workflow that pages the on-call engineer when Affected system is set to a production system, or that notifies finance when Cost exceeds a threshold. Field rules belong to a ticket type, so each type has its own rules. They’re available on every ticket type that has custom fields, including requests, incidents, problems, tasks, journeys, change models, and custom types.

Create a field rule

1

Open the ticket type

Go to Settings → Ticket Types, select the ticket type, and open the Fields tab. The Field rules card is below the custom fields.
2

Start a rule

Select Create rule and enter a Rule name.
3

Add conditions

Under If, select Add condition, choose a Field and a Condition, and enter the value to compare against. Add more conditions as needed, and use Combine to choose OR, so any one can match, or AND, so every condition must match. To mix the two, select Add group to nest a group of conditions one level deep.
4

Choose the workflow

Next to Run, choose a published workflow.
5

Save

Select Create rule. New rules start enabled.
Rules compare each field to a value. You can’t compare one field to another or check who made the change.

Conditions by field type

Only active fields of the ticket type appear in the Field list.

When a rule runs

A rule is checked when a ticket is created or updated and the change sets or changes at least one of the fields its conditions use. Serval then evaluates all the rule’s conditions against the ticket’s new values and runs the workflow only if they match. Changes to other fields don’t trigger the rule.
  • Every rule that matches starts its own workflow run.
  • Changes made by workflows, including the rule’s own workflow, don’t trigger rules.
  • When a ticket is converted to another type, the new type’s rules don’t run on the values carried over.
The workflow runs on the ticket, so it can read the ticket and its custom fields. It also receives each changed field’s previous and new value. The workflow can’t require confirmation to start or have required inputs. Its result isn’t used, and a failed run doesn’t undo the field change.

Manage rules

The Field rules card lists each rule with its conditions, the workflow it runs, and its status. Rules are listed oldest first. From a rule’s menu, select Edit, Disable or Enable, or Delete. Deleting a rule stops it from running for new changes. Runs that already started aren’t affected. You need the Builder role or higher to create, edit, or delete rules. The Read-Only Agent role and higher can view them. The change model Serval installs is read-only, so to add rules to it, clone it first.

Deprecated conditions

Rules created before the current editor can use conditions that aren’t offered anymore, such as “changed from,” “increased,” or conditions on who made the change. These rules show a Deprecated badge and keep running as saved. You can rename them, enable or disable them, or change their workflow. To edit their conditions, replace every option marked Deprecated with a supported one.

Custom Fields

Add the structured fields that rules check

Workflows

Build the workflow a rule runs