Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 457066

Summary: Change of process in Pending Closure Notifications
Product: [Retired] JBoss Customer Support Portal Reporter: Mike Amburn <mamburn>
Component: NotificationsAssignee: JBoss CSP Bug Watch List <csp-bugs-watch>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: medium    
Version: 1.3.8Keywords: FutureFeature
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: 1.3.9 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-07-29 14:47:59 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: 457070    

Description Mike Amburn 2008-07-29 14:46:58 UTC 
As of today, Pending closure is based on the following procedure:
Red Hat Support engineer commits a manual comment and, in Issue Tracker, he
manually sets the case status to 'Pending closure' Often at the same time the
technician will make a comment. This could generate 2 notifications under
today's logic; one for the comment, a second for the status change to Pending
Closure.

If a comment and status change is made to flip to Pending Closure, the system
must send only one notification to the customer that includes the comment and
the pending closure status change

If the comment is committed, then the status change is committed (or vice
versa), the system must detect that condition and send only one notification to
the customer that includes the comment and the pending closure status change

If a status change is made to Pending Closure and no comment is made within the
notifications time period, send a generic email saying that the case has been
moved to pending closure. Text to be provided in update to JIRA.
Comment 1 Mike Amburn 2008-07-29 14:47:59 UTC 
Should be included in 1.3.9 according to Jira.
https://jira.jboss.org/jira/browse/JBNET-2258