Priority Calculation
On this page
A ticket's priority can be derived from its impact and its urgency. The rule is set per service level: each service level carries a priority matrix with one row per impact and one column per urgency, and every cell names the priority for that pair. The matrix uses the impact, urgency, and priority values of the level's class.
The derived priority is also the priority by which the service level's response and resolution targets are looked up.
The matrix is the Priority Calculation table of a service level, which is edited in the Web App on the service. Services are a Service Management item of the Web App navigation, available only where the ITSM module is licensed. The procedure is in Services and SLAs.
How the calculation works
- The priority is taken from the matrix of the service level that applies to the ticket, for the pair of the ticket's impact and urgency.
- If that service level has no entry for the pair, the calculation returns no priority.
- The calculation does not check whether a value is active. An inactive impact, urgency, or priority still takes part when a matrix entry names it.
- The calculation runs when a workflow macro calls it; the database does not run it on its own. If the workflow does not call it, the matrix is not applied. For the workflow, see Workflow Overview.
Automatic prioritization in the supplied configuration
A new 2026.1 database created with the Default Workflow contains workflow triggers that apply the priority matrix to tickets. An upgraded database need not contain them, and an administrator may have changed them. See Default Workflow Configuration.
- Incidents, problems, change requests, service requests, and work orders each have a trigger named Set Priority Calculation, with the description "Used to set Priority, Response Date and Due Date", of the kind On Created/Modified. The five triggers are enabled in the supplied configuration.
- A trigger fires only when Service, Impact, and Urgency are all filled in on the ticket and at least one of Service, Requester, Impact, Urgency, Priority, or Submit Date has been changed. On service requests, the trigger checks Organization in place of Requester.
When the trigger fires, it does one of two things:
- If Priority has not been changed, it sets Priority from the Calculate Priority macro, which reads the priority matrix, and then sets Response Date and Due Date from the Calculate Response Date and Calculate Due Date macros.
- If Priority has been changed, it keeps the new priority and sets only Response Date and Due Date, from that priority.
On incidents, both branches then run Set Response Overdue and Set Resolution Overdue.
Inactive values and unset cells
In the Web App's service level panel, the Priority Calculation table and the Ticket Response and Resolution Targets table each have their own Show inactive items switch. Both are off the first time the panel opens; if the panel is closed and reopened without reloading the page, each switch keeps the position it was left in.
- With the switch off, the Priority Calculation table takes its rows, its columns, and the priorities in every cell from the active impacts, urgencies, and priorities only, and the targets table leaves out the rows of inactive priorities.
- With the switch on, inactive values are shown too.
The switch changes only what the tables show. When the panel is saved, it saves an entry for every pair of impact and urgency, including pairs hidden by the switch, and a target row for every priority. A pair that has no stored priority starts with the first priority of the full priority list, inactive priorities included, so an untouched cell carries a priority rather than none. Because the calculation does not check whether a value is active, a matrix entry for a value that was deactivated after use still counts.