Bug 453605 - (RFE) Turn off CSP new case notifications to product groups
Summary: (RFE) Turn off CSP new case notifications to product groups
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Customer Support Portal
Classification: Retired
Component: Web-General
Version: 1.3.9
Hardware: All
OS: Linux
high
low
Target Milestone: ---
: ---
Assignee: JBoss CSP Bug Watch List
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-07-01 14:55 UTC by John Sanda
Modified: 2008-08-21 07:32 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-08-21 07:32:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description John Sanda 2008-07-01 14:55:05 UTC
Description of problem:
When a customer creates a new case, two notifications are sent to the support
team(s), one from GateKeeper and one from the CSP. The one from the CSP has a
sbject line that reads something like, "New case notification. Case Number
[177963]". The subject line from the GateKeeper email reads like, "New Events
for Red Hat Case# 177963".

We need to turn off the new case notifications sent by the CSP to the product
group as they are no longer needed. From the business perspective, we should:

1) Send just one email when the case is created.

2) Look at group preferences. If a support tech does not want email
notifications, then don't send them.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Frank Merenda 2008-07-01 15:43:01 UTC
(11:40:05 AM) nlugert: if anyone is curious, the bug that was fixed for the test
John was doing that brought up discussion was to fix a notification that was
immediately sent to an *employee* that opened a case via CSP stating that there
are new events on the case they had just opened. This was only sent if the
person that opened the case in the CSP was an employee. This new one has never
been declared a bug.


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