A ticket needs a nonblank system Priority before an SLA policy can apply. A custom field with the same display name does not satisfy that requirement. Active policies are ordered, and the first matching policy supplies the targets. Triggers run before SLA evaluation, so a trigger can establish priority first. Keep the ticket population separate from the targets by priority; the policy already represents priority and status behavior rather than treating them as arbitrary ordinary filter fields.
Inspect the current ticket and policy result together. Later tasks change the population or hour basis so the first example cannot be copied without thought. This model supports selected first reply, next reply and resolution calculations. It discloses its UTC business schedule and does not reproduce every production SLA option.
Worked example: system priority and policy order.