Rocketship now supports regular expressions (regex) for matching ticket titles. Regex gives you more control when defining match rules — you can match patterns instead of exact words.
This allows you to automatically group, escalate, or schedule tickets based on more flexible title patterns.
Common Regex Patterns
Word Boundaries
Use \b to match a whole word and avoid partial matches.
Regex:
\bWORD\b
Matches:
WORD
Does not match:
WORDLESS
MYWORD
Digits
Use \d to match numbers.
Regex:
\d+
Matches:
Ticket 123
Error 42
Does not match:
Ticket ABC
Whitespace
Use \s to match spaces, tabs, or line breaks.
Regex:
Task\sComplete
Matches:
Task Complete
Does not match:
TaskComplete
Start and End of Line
Use ^ to match the start of a title, and $ to match the end.
Regex:
^Urgent$
Matches:
Urgent
Does not match:
Urgent Ticket
Zero or More
Use * to match zero or more of the previous character.
Regex:
Hel*o
Matches:
Heo
Helo
Hello
One or More
Use + to match one or more of the previous character.
Regex:
Hel+o
Matches:
Helo
Hello
Helllo
Does not match:
Heo
Example
To match only ticket titles that start with “Error” followed by a space and a number:
Regex:
^\bError\s\d+\b$
Matches:
Error 404
Does not match:
Critical Error 404
Tip
You can test regex patterns on sites like regex101.com before adding them to your rules.
Related Articles
How to Test Ticket Criteria for Escalation Rules in Autotask
When creating Escalation Rules, you will define Ticket Criteria to match a ticket against an Escalation Rule. How to test Ticket Criteria The best way to test Ticket Criteria, i.e., to check which Escalation Rule will match a given Autotask Ticket, ...
Troubleshooting Escalation Rules: Common Reasons for Non-Matching Tickets
Escalation Rules map tickets in Autotask to escalation paths used by Rocketship to assign and (if configured) automatically schedule resources. At times, a ticket may not match an Escalation Rule. This KB describes how to troubleshoot when an ...
Multiple Ticket Matching Criteria for Escalation Rules
To streamline your workflow and reduce administrative overhead, we have updated the Escalation Rule engine. You can now define multiple Ticket Matching Criteria within a single Escalation Rule. Now, you can consolidate these into one rule by adding ...
How to handle a Team being overloaded via Ticket Routing
There are times when a Team may be overloaded with work while other Teams are not. For example, let’s say you have a Ticket Routing Rule named HelpDesk that has this Escalation Path: QuickFix Team [Bob, Sue, Phil] Tier 2 Team [Jill] Tier 3 Team ...
Using Ticket Routing to Automate Dispatch & Escalations
With Rocketship for Autotask, it is easy to use ticket routing to automate dispatch & escalations. Ticket routing is how you shuffle tickets around – whether it’s a dispatch, which is assigning a ticket to a resource when there’s been no assignment ...