Bug 451134

Summary: If Initial Response Time does not run on a case, Sub response time will never set
Product: [Retired] JBoss Customer Support Portal Reporter: Mike Amburn <mamburn>
Component: GatekeeperAssignee: JBoss CSP Bug Watch List <csp-bugs-watch>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 1.3.9CC: fmerenda
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard: Completed Sprint #5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-08-20 16:20:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 451141    

Description Mike Amburn 2008-06-12 22:46:13 UTC 
If Initial Response time never runs on a case, then Subsequent Response time
rule will never set the case expiration date as it is expecting that field to be
populated by the Initial Response Time Rule. Remove this expectation.
Comment 1 Nathan Lugert 2008-06-16 11:27:04 UTC 
To Test:

1. Create a case in the CSP

2. Immediately add a public comment as a technician and set case status to
Waiting on Customer. (This needs to be done right after creating the case and
before GK runs and sets the Initial Response Time)

3. Verify Gatekeeper runs after above comment and Time to Service Breach is set
correctly