Bug 449027 - Initial notification for case change of group not being sent
Initial notification for case change of group not being sent
Product: Issue-Tracker
Classification: Retired
Component: Notifications (Show other bugs)
All All
medium Severity medium
: ---
: ---
Assigned To: Mike Amburn
Depends On:
  Show dependency treegraph
Reported: 2008-05-29 17:45 EDT by Mike Amburn
Modified: 2012-06-26 16:47 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2012-06-26 16:47:44 EDT
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-05-29 17:45:29 EDT
Initial notification for case change of group not being sent - may be firewall,
may be bug.

When a case is changed in issue tracker from one group to another (escalated)
notifications go out when a change to the case is made.

The users are not getting the initial notifications that they have new cases in
their queue (A new case has been entered in your queue).

I believe that this is what is happening:

- csp sends notifications on case changes, new attachment, new comment, status
change, etc. All users in the product group.
- csp sends notification of new case to all people in the product group when a
new case is created.
- if a case is in a group, and gets escalated, i.e. from jboss support to jboss
- ON, the ON group never gets any notification
  at all on initial assignment of the case. They will get subsequent notifications.

I believe that what is happening is:
- case escalated to internal jboss group
- case doesn't change anything else
- no notification is being sent out
- IT doesn't send out the notification because it's a jboss group.
Comment 1 Mike Amburn 2012-06-26 16:47:44 EDT
Closing my open Issue-Tracker requests.

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