A trigger evaluates saved ticket events. Define the intended population with All and Any, then specify the fields the rule changes. A rule can be active and still do nothing when its conditions exclude the ticket. Test one ticket that should match and another that must stay unchanged. Saving the trigger is configuration work; submitting a qualifying ticket update is the execution event that proves the outcome.
Start with the required population and inspect the resulting saved fields. The first task supplies the steps; later tasks change the source conditions and ask you to preserve a control record. The workspace executes a disclosed subset of ticket rules locally and never sends a notification to an operational account.
Worked example: trigger conditions and actions.