Bug 451134 - If Initial Response Time does not run on a case, Sub response time will never set
If Initial Response Time does not run on a case, Sub response time will never...
Status: CLOSED CURRENTRELEASE
Product: JBoss Customer Support Portal
Classification: Retired
Component: Gatekeeper (Show other bugs)
1.3.9
All All
medium Severity low
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
Completed Sprint #5
:
Depends On:
Blocks: 451141
  Show dependency treegraph
 
Reported: 2008-06-12 18:46 EDT by Mike Amburn
Modified: 2008-08-20 12:20 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-08-20 12:20:36 EDT
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-06-12 18:46:13 EDT
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 07:27:04 EDT
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 

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