Allow Service Level Targets to be based on an alternate starting time.

Idea ID 2762549

Allow Service Level Targets to be based on an alternate starting time.

Use case :

When an Incident is created as part of an escalation from a Support Request, the SLA of the request will already exist for a certain time.

It should be possible to take that time already spent at the request level into account when calculating the remaining time at the incident level.

Problems with current implementation of fully independent SLA calculations on requests and incidents:

  • Escalated incidents need to be resolved within the resolution time allowed by the request SLA. This time is however not predictable
  • There is no way to let incident SLA calculations take into account the time spent at the request level before escalation to the incident

A mechanism such as the following would allow handling this used case properly :

  • When the request is escalated to a new incident, the request create time is copied to a new incident field (e.g. InitialRequestStartTime_c). (this can either be done via custom After adding relationship rule or be implemented as an OOTB functionality as part of this change)
  • NEW FUNCTIONALITY: Allow the Incident SLT calculations to be based on this field instead of the Incident creation time.

Note : when relating a request to an existing Incident, two options will exist:

  1. keep the existing InitialRequestStartTime_c (if any). This means that the Incident SLT calculations will be based on the initial escalation time
  2. OPTIONAL / IF FEASIBLE: keep the earlier time (either InitialRequestStartTime_c or the create time of the newly related request).

  This will then base the Incident SLT calculations on the related request that has been reported first

  (requires SLT calculations to dynamically use this datetime field)

Benefit :

  • Incident Service Level Targets can be made to represent overall customer service level targets, as defined at the level of the request.

  Any time spent during the attempted resolution at the level of a request will be taken into account at the level of the Incident

Tags (1)
1 Comment
Micro Focus Frequent Contributor
Micro Focus Frequent Contributor
Status changed to: Waiting for Votes

Thank you for sharing your idea! It’s open for comments and kudos, and we’re looking forward to input from the community. Once there is enough community traction, it will be further reviewed by the product team.

The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.