Bug 454542 - Modify verbiage in the GK process logs
Modify verbiage in the GK process logs
Product: JBoss Customer Support Portal
Classification: Retired
Component: Gatekeeper (Show other bugs)
All All
low Severity medium
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
Depends On:
  Show dependency treegraph
Reported: 2008-07-08 17:47 EDT by Mike Amburn
Modified: 2009-02-09 15:59 EST (History)
2 users (show)

See Also:
Fixed In Version: MR8-CSP
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-01-30 15:50:05 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
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:47:56 EDT
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 15:59:58 EST
Modified verbiage to be more readable. Specifically for notifications. Logs when a user is sent a notification and whenever a group notification is sent.

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