You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

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:

  1. Low
  2. Medium
  3. High
  4. Very High

The urgency of the issue measures the time until the issue affects the business. In SimpleOne, the urgency is classified  as follows:

  1. Low
  2. Medium
  3. High
  4. Very High


The priority of the issues is classified as follows:

  1. Low
  2. Moderate
  3. High
  4. Critical

The priority matrix

Impact / UrgencyLowMediumHighVery High
LowLowLowModerateHigh
MediumLowModerateModerateHigh
HighModerateModerateHighCritical
Very HighHighHighCriticalCritical

Extend the priority matrix

Add impact and urgency options


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:

  1. Open the record of any issue that has an impact or urgency field.
  2. Right-click the title of the field you need and select Configure field from the context menu appeared.
  3. In the Related Lists area, select the Choice tab.
  4. Click New, fill in the fields.
  5. Click Save or Save and Exit to apply the changes.

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:

  1. Navigate to the Task table.
  2. Open any record, right-click the Urgency field title and choose Configure field option from the context menu that appeared.
  3. In the Related Lists area, select the Choice tab.
  4. Click New and fill in the fields.
    1. Enter Critical in the Title field.
    2. Enter 5 in the Value field because the value for Very High is 4.
  5. Click Save or Save and Exit to apply the changes.

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.

Add new priority combinations


After adding new choice options, extend the priority matrix. To do this, complete the steps below:

  1. Navigate to Data Matching Definition Priority Matrix.
  2. Click New and fill in the fields.
  3. Click Save or Save and Exit to apply the changes.

Priority Matrix form field

FieldMandatoryDescription
ImpactNThe impact value you plan to use in the new priority value.
UrgencyNThe urgency value you plan to use in the new priority value.
PriorityNThe priority value that is calculated based on the impact and urgency.
ApplicationNThe application that this priority value is related to.
PolicyN

The current record protection policy. Available options:

  • Open
  • Changed
  • Protected
OrderNThe 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 / UrgencyLowMediumHighVery High
Very LowLowLowLowModerate
LowLowLowModerateHigh
MediumLowModerateHighCritical
HighModerateHighCriticalCritical
Very HighCriticalCriticalCriticalCritical

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.

  • No labels