While a Ticketing Application has the ability to configure a Priority Matrix in Shared Ticketing Settings, it requires the Priority ticket attribute to be editable on a ticket form to function. In addition, the Priority Matrix is a shared setting, meaning that the matrix is shared between multiple ticketing applications in your TDX Environment.
In scenarios where you'd like to set a dynamic Priority at Ticket creation and not make the Priority attribute editable on a form, you can leverage Automation Rules!
Scenario - Example Priority Matrix
|
Urgency
|
Impact
|
LOW
|
MEDIUM
|
HIGH
|
USER
|
LOW
|
LOW
|
MEDIUM
|
GROUP
|
MEDIUM
|
MEDIUM
|
HIGH
|
DEPARTMENT
|
MEDIUM
|
HIGH
|
HIGH
|
ORGANIZATION
|
MEDIUM
|
HIGH
|
EMERGENCY
|
Example Automation Rules
The following Automation Rules replicate the above example Priority Matrix within Automation Rules.
For information on creating Automation Rules, please review Getting Started with Automation Rules
LOW Priority RULE
- Urgency is one of [LOW, MEDIUM]
- Impact is one of [USER]
MEDIUM Priority RULE
- Urgency is one of [HIGH]
- Impact is one of [USER]
- Urgency is one of [LOW, MEDIUM]
- Impact is one of [GROUP]
- Urgency is one of [LOW]
- Impact is one of [DEPARTMENT, ORGANIZATION]
Set Advanced Filter:
- (1 AND 2) OR (3 AND 4) OR (5 AND 6)
HIGH Priority RULE
- Urgency is one of [HIGH]
- Impact is one of [GROUP]
- Urgency is one of [MEDIUM, HIGH]
- Impact is one of [DEPARTMENT]
- Urgency is one of [MEDIUM]
- Impact is one of [ORGANIZATION]
Set Advanced Filter:
- (1 AND 2) OR (3 AND 4) OR (5 AND 6)
EMERGENCY Priority RULE
- Urgency is one of [HIGH]
- Impact is one of [ORGANIZATION]
The above examples can be adjusted and changed to meet the needs of an organization and their priority assignment logic. One thing to keep in mind is that this approach only assigns a priority at the time a ticket is created, as that is when automation rules are engaged.