Priority calculation is a predefined set of values that automatically set Priority, Urgency, and Impact values on problems and incident tickets.
Note: If you migrated from a previous release, the priority calculation values must be enabled after the migration. For more information about enabling priority calculation, see the Implementation Guide.
You can define a priority calculation to handle, incidents, problems, or both. However because two priority calculations cannot handle the same ticket type, you can review and update existing priority calculations before you create ones. For example, if you want to add a priority calculation to manage problem tickets, first clear the Problem field on the active priority calculation. Then, create a priority calculation to manage problem tickets.
If multi-tenancy is installed, you can use one public priority calculation that applies to all tenants or several tenant-specific priority calculations.
Note: For information about how priority calculation manages ticket values or tenants, see the Administration Guide.
To define a priority calculation
The Priority Calculation List page appears.
The Create Priority Calculation page appears.
Identifies the priority calculation.
Specifies the ticket status for this priority calculation.
Specifies whether this priority calculation applies to incident ticket types.
Specifies whether this priority calculation applies to problem ticket types.
Verifies the spelling of text in the Description field.
Specifies the purpose of the priority calculation.
Specifies the initial Impact value to display when the user creates a ticket.
Works with the Impact Increment field. Specifies whether the user can override the ticket Impact value with the Impact level specified in the attached Affected Service.
Works with the Override Impact field. Increments the Impact by the specified amount when the user overrides the Impact value. When the ticket uses a blackout window, the Impact value increments only when the open date is within the blackout window time frame. The Impact value can only raise to a maximum of 1-High. For example, if you set the value to 2 and the default Impact is 3-Medium, the user can only override the Impact on a ticket to 1-High.
Specifies the Urgency value to display when the user creates a ticket.
Specifies whether the user can override the ticket Urgency value with the Area Urgency level specified in Incident or Problem area.
Works with the Override Urgency field. Increments the Urgency level by the specified amount when the affected end user sets the Escalate Urgency flag.
Specifies whether the user is required to enter the reason for changing the Urgency or Impact values. If the user changes the Urgency or Impact values, the Escalate Detail page appears while saving the ticket. The user is required to describe the reason for changing the Urgency or Impact values.
Specifies whether to use the priority calculation for tickets that use templates.
The default values reset.
The Update Priority Detail page appears. On the next new or updated ticket or Knowledge Document, the fields update according to the values in the active priority calculation. If no priority calculation is active for a ticket type, the system clears the Priority, Urgency, and Impact fields.
Copyright © 2013 CA.
All rights reserved. |
Tell Technical Publications how we can improve this information |