Bug 457066 - Change of process in Pending Closure Notifications
Change of process in Pending Closure Notifications
Status: CLOSED CURRENTRELEASE
Product: JBoss Customer Support Portal
Classification: Retired
Component: Notifications (Show other bugs)
1.3.8
All All
medium Severity low
: ---
: ---
Assigned To: JBoss CSP Bug Watch List
: FutureFeature
Depends On:
Blocks: 457070
  Show dependency treegraph
 
Reported: 2008-07-29 10:46 EDT by Mike Amburn
Modified: 2008-07-29 10:58 EDT (History)
0 users

See Also:
Fixed In Version: 1.3.9
Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-07-29 10:47:59 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-07-29 10:46:58 EDT
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 10:47:59 EDT
Should be included in 1.3.9 according to Jira.
https://jira.jboss.org/jira/browse/JBNET-2258

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