[#CHD-1450] [Home Notifications] "New Ticket Assignment" generated when another worker replies - WebGroup Media LLC - Projects

Issue Details [XML]

Key:	CHD-1450
Type:	Improvement
Status:	Resolved
Resolution:	Fixed
Assignee:	Jeff Standen [WGM]
Reporter:	Joe Geck
Votes:	0
Watchers:	0

Operations

Clone this issue

If you were logged in you would be able to see more operations.

Cerberus Helpdesk

[Home Notifications] "New Ticket Assignment" generated when another worker replies

Created: 06/Oct/09 03:06 PM Updated: 16/Jul/10 04:05 PM

Fix Version/s:

5.0 RC1

Original Estimate:

Unknown

Remaining Estimate:

Unknown

Time Spent:

Unknown

Description

Summary:
Reported by a user, but apparently we've experienced this internally too.

Steps:
0) Use two workers for this test.
1) Assign a ticket to Worker A.
2) For Worker A, go to 'my account' and create a Watcher filter. Choose...

"Assigned to self" event
"Send a worker notification" (not the e-mail one)

3) Login as Worker B, find that assigned ticket, and reply. Leave the ticket assigned to Worker A.
4) Check 'home' notifications in Worker A's account.

Result:
"New Ticket Assignment" notification appears.

Note:
This problem does not affect Watchers (e-mail) notifications.

All

Comments

Work Log

Change History

Sort Order:

Comment by Joe Geck [06/Oct/09 03:08 PM]

[ Permlink ]

E-mailed to us.
---
Can I edit how notifications are triggered? (I like how it gives notifications when manually selected or when someone gets assigned a ticket but I do not like how it creates a notification when someone else works on a ticket assigned to you.)

Comment by Joe Geck [08/Oct/09 07:44 AM]

[ Permlink ]

Additional notes:
Hildy just reported in our live desk that he got an assignment notification for a closed ticket I replied to and left closed.

Comment by Jeff Standen [WGM] [25/Apr/10 10:54 AM]

[ Permlink ]

This shouldn't be happening anymore in Cerb5 RC1 because the auto-take no longer happens in replies.

Comment by Jeff Standen [WGM] [25/Apr/10 11:29 AM]

[ Permlink ]

Fixed in 5.0 RC1