Bug 454551 - New specs for Service Breach Time Calculations
New specs for Service Breach Time Calculations
Status: CLOSED CURRENTRELEASE
Product: JBoss Customer Support Portal
Classification: Retired
Component: Gatekeeper (Show other bugs)
1.3.9
All All
high Severity high
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
:
: 454717 (view as bug list)
Depends On:
Blocks: 457070
  Show dependency treegraph
 
Reported: 2008-07-08 17:52 EDT by Mike Amburn
Modified: 2009-02-09 16:07 EST (History)
2 users (show)

See Also:
Fixed In Version: MR8-CSP
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-01-30 15:24:06 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike Amburn 2008-07-08 17:52:56 EDT
There are four situations when SBT notifications should be sent to JBoss Support.
case status is NEW and Threshold Time is reached
case status is NEW and Breach Time is reached
case status is WORH and Threshold Time is reached
case status is WORH and Breach Time is reached

Service Breach Time notifications
These four situations need to be managed by four different rules in GateKeeper because we need the ability to turn on or off these four rules independently from each other.

Values of Threshold time according to Initial Response Time
Initial Response Time | Threshold Time 1 hour | 40 minutes before Breach 2 hours | 40 minutes before Breach 4 hours | 1 hour before Breach 4 business hours | 1 hour before Breach 24 hours | 4 hours before Breach 1 business day | 4 hours before Breach 2 business days | 12 hours before Breach

***These values should be configurable, so that we can easily change Warning Threshold Times in the future
*** Either through a ui, or deployable drools file. Value of the Subject field in the email template 

The template is the same for the 4 situations mentioned above, EXCEPT for the Subject of the email Case status is NEW and Threshold Time is reached [I-T group]-[tid] : NEW Case - IMPENDING SLA BREACH - [case summary] Case status is NEW and Breach Time is reached [I-T group]-[tid] : NEW Case - BREACHED SLA - [case summary] Case status is WORH and Threshold Time is reached [I-T group]-[tid] : WORH Case - IMPENDING SLA BREACH - [case summary] Case status is WORH and Breach Time is reached [I-T group]-[tid] : WORH Case - BREACHED SLA - [case summary]

Email template
-------------------------------------------------------------
From: no-reply@redhat.com
To: [I-T user's email address]
Subject: [Depends on specific case situation - See section above]

Case Url: [link to case]
Case Number: [tid]
Severity: [case severity]
Service Breach Time: [Service Breach Time]
Contact Name: [name of person who opened the case]
Case Company: [company name]
Contact Phone: [contact phone of person who opened case]
Customer Email: [email address of person who opened case]
Case assigned to: [name of the case owner] and, if not = 'not assigned yet'
Product Selected: [product]
Version Selected: [version]
Module Selected: [module]
Case Summary: [case summary]
Case Description: [Full case description] -------------------------------------------------------------

----
Data relocated from Jira (JBNET-2260)
Comment 1 Nathan Lugert 2008-08-28 09:06:17 EDT
*** Bug 454717 has been marked as a duplicate of this bug. ***
Comment 2 Nathan Lugert 2009-02-09 16:07:00 EST
implemented new SLA breach specifications. Threshold can be set without re-deploy of Gatekeeper as they are JBPM variables. I set SLA breach threshold times to that of the description. 

Also, updated the impending SLA Breach email notification template to match the one in the description.

Note You need to log in before you can comment on or make changes to this bug.