The priority of an ITSM ticket can be figured out based on its impact and urgency using a priority matrix.
The impact of an issue indicates the measure of the potential effect on the business user or service or CI. In SimpleOne, the impact can be categorized as:
The urgency of an issue indicates the measure of time until an issue has an impact on the business. In SimpleOne, the urgency can be categorized as:
Based on the priority, issues can be categorized as:
The priority matrix
|
Generally, the priority matrix is provided "as-is", filled with standard settings, but you can customize it, basing on your business tasks and priorities. The first thing to do is to add more impact and/or urgency options.
To add new impact or urgency options, please perform the following steps:
Field | Mandatory | Description | |
---|---|---|---|
Table | Y | A table where to add a choice option. This field is populated automatically. | |
Column | Y | A column where to add a new record. This field is populated automatically. | |
Title | Y | New option title. | |
Language | Y | In there, specify the two-symbol name of the language (ru, en, and so on). Generally, references to languages are stored in the Languages (sys_language) table. | |
Value | Y | The option value. This is a numeral field.
| |
Order | Y | Option order. It grows in the ascending order. | |
Hint | N | A text hint. |
After you have added a choice option for a table, perform the same action for the Priority Matrix (itsm_dl_priority) table. The action sequence will be the same. |
In this example we create a new option for urgency field for the Task table. The new option will be "Critical".
To do that, perform the following steps:
After we have added "Critical" choice option for the Urgency field in the Task table, we perform the same action for the Priority Matrix (itsm_dl_priority) table. The action sequence is the same.
When you're done, you are ready to extend the priority matrix.
To do this, please complete the steps below:
Priority Data Lookup 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 figured out based on the impact and urgency. |
Application | N | The application to which this priority value is related. |
Policy | N | The current record protection policy. Available options:
|
Order | N | The priority position on the list. |
Repeat these actions until your priority matrix covers all the possible combinations of the impact and urgency.
Urgency / Impact | Very High | High | Medium | Low | Very Low |
---|---|---|---|---|---|
Low | Critical | Moderate | Low | Low | Low |
Medium | Critical | High | Moderate | Low | Low |
High | Critical | Critical | High | Moderate | Low |
Very High | Critical | Critical | Critical | High | Moderate |
Please keep in mind that if you want priorities to change dynamically in your task objects depending on selected impact and urgency values, you have to implement relevant client logic designated as a client script for the Task table. For this, process these metrics value changes and select appropriate value from the itsm_dl_priority dictionary. |