Trigger order affects intermediate ticket values. After a trigger changes a ticket, evaluation starts again; a trigger that already fired cannot fire again within that same update cycle. An earlier false rule can become true after a later rule supplies a field. Inspect the resulting audit sequence rather than assuming the system makes one pass through a list. Competing field changes can leave a valid-looking configuration with the wrong final value.
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 re-evaluation and order.