Bug 454542

Summary: Modify verbiage in the GK process logs
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: medium Docs Contact:
Priority: low    
Version: 1.3.9CC: fmerenda, nlugert
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: MR8-CSP Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-01-30 20:50:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Mike Amburn 2008-07-08 21:47:56 UTC
Some verbiage in the Gatekeeper process logs is either using the wrong words or mis-representing what is actually happening. May need to add additional log messages as well for better run reporting. Some examples of bad verbiage:

Subsequent Response Time Rule : ALERT: Case [ID=157893] processing error : Last Comment/Attachment time is null

What really is happening in this situation is the ticket is Waiting on Red Hat but the last comment/attachment posted is from a Red Hat employee and not from a customer. We should either say this or setup subsequent response time to use the last customer comment/attachment regardless if a RH employee has commented. Also, Subsequent Warning Email Rule says Set instead of Sent

----
Data relocated from Jira (JBNET-2274)

Comment 1 Nathan Lugert 2009-02-09 20:59:58 UTC
Modified verbiage to be more readable. Specifically for notifications. Logs when a user is sent a notification and whenever a group notification is sent.