Outcome. Every ticket that reaches a specific pipeline stage gets its priority set consistently, instead of relying on whoever moves it to also remember to update priority by hand.
Workflow map
Enrollment, branches and actions at a glance
tickets-sla-035
flowchart TD
A[Ticket enters Escalated stage] --> B{Priority already High or Urgent?}
B -->|no| C[Set priority to High]
B -->|yes| D[No action, keep existing priority]
When to use it, when not to
- UseUse it when a pipeline stage itself implies a priority level, for example an "Escalated" stage that should always carry at least High priority regardless of what it was set to at intake.
- UseUse it as a simple guardrail, not a replacement for tickets-sla-002 or tickets-sla-025's intake-time priority logic; this fiche only reacts to a stage change, it does not set priority at creation.
- SkipDo not use it on a stage that does not have a consistent priority implication; if "In progress" can reasonably be any priority level, forcing one value on stage entry destroys real signal.
- SkipDo not use it to downgrade priority automatically on stage change without checking tickets-sla-018, which covers priority downgrade specifically and may already do this in the direction you want.
The preview ends here. Six sections are in the library.
counted, not blurred
PrerequisitesEvery property with its label, internal name, type and options, plus the assets the workflow needs before you start.2 items
EnrollmentThe trigger, the criteria exactly as they are ticked in the UI, the re-enrollment rule and the suppression list.4 parts
StepsEach action in order with its parameters, its branches and its delays, written as you tick them.3 numbered actions
Known pitfallsTraps seen in production, each with what breaks and what to do instead.4 pitfalls
Test plan, variants and build specHow to prove it works in a test portal, where to look when it does not, the variants for other objects or tiers, and the YAML build spec.3 variants, 3 sections
FilesThe properties JSON creates the fields in one API call, the workflow JSON documents the build.PDF, Markdown, JSON
Install1 click. The installer creates the properties this spec declares and the workflow itself, switched off, then opens a task for the prerequisites that are assets rather than properties, such as a team, a static list or a marketing email. What it created is listed on the install page.1 click, switched off
Unlock the full library,
149 EUR
or the tickets and sla pack, 39 EUR
One-time, excl. VAT. 30-day refund, no questions asked. Founding prices until 31 October, then 199 and 59 EUR. Includes every spec added later, up to the full 500, and the one-click installer on the full library. Building on client portals? The agency licence at 449 EUR covers unlimited client portals.
