The priority of an ITSM ticket can be figured out based on its impact and urgency using a priority matrix.
The impact of the issue measures the potential effect on the business user, service, or CI. In SimpleOne, the impact is classified as follows:
The urgency of the issue measures the time until the issue affects the business. In SimpleOne, the urgency is classified as follows:
The priority of the issues is classified as follows:
The priority matrix
|
The "out-of-the-box" solution has a priority matrix with standard settings, but you can customize it, based on your business tasks and priorities. Firstly, add more impact and/or urgency options.
To add a new impact or urgency option, perform the following steps:
See the Choice Fields article to learn how to create choice options.
The Value field should be filled in according to the rule: the value must be relevant to the impact or the urgency. For example, the High option of Impact has a value of 3. If you add a Very High option for Impact that is higher than High, increase the value to 4. And if you add the Medium option for Impact that is lower than High, decrease the value to 2. |
After you have added a choice option for a table, perform the same for the Priority Matrix (itsm_dl_priority) table. The action sequence is the same.
Example
You need to create the Critical option for the Urgency field of the Task table. To do this, perform the following steps:
After you have added Critical choice option for the Urgency field in the Task table, perform the same action for the Priority Matrix (itsm_dl_priority) table. The action sequence is the same.
After adding new choice options, extend the priority matrix. To do this, complete the steps below:
Priority Matrix form field
Field | Mandatory | Description |
---|---|---|
Impact | N | The impact value you plan to use in the new priority value. |
Urgency | N | The urgency value you plan to use in the new priority value. |
Priority | N | The priority value that is calculated based on the impact and urgency. |
Application | N | The application that this priority value is related to. |
Policy | N | The current record protection policy. Available options:
|
Order | N | The priority position on the list. |
Repeat these steps until your priority matrix covers all the possible combinations of the impact and urgency.
Extended priority matrix (example)
Impact / Urgency | Low | Medium | High | Very High |
---|---|---|---|---|
Very Low | Low | Low | Low | Moderate |
Low | Low | Low | Moderate | High |
Medium | Low | Moderate | High | Critical |
High | Moderate | High | Critical | Critical |
Very High | Critical | Critical | Critical | Critical |
If you need the priorities in your task objects to change dynamically based on the selected impact and urgency values, implement the appropriate client logic in a client script for the Task table. To do this, process the changes in the values of these metrics and select the appropriate value from the itsm_dl_priority dictionary. |