History | Log In     View a printable version of the current page. Get help!  
Issue Details [XML]

Key: CHD-570
Type: Bug Bug
Status: Open Open
Assignee: Jeff Standen [WGM]
Reporter: Joe Geck [WGM]
Votes: 10
Watchers: 6
Operations

Clone this issue
If you were logged in you would be able to see more operations.
Cerb4 (Cerberus Helpdesk 4.0)

Incoming/Outgoing labels are switched when an e-mail is sent to the Helpdesk from a worker address

Created: 14/Mar/08 01:33 AM   Updated: 13/Nov/08 03:06 PM
Fix Version/s: 4.0 - Milestone #22

Original Estimate: Unknown Remaining Estimate: Unknown Time Spent: Unknown


 Description   
Summary:
http://www.cerb4.com/forums/showthread.php?t=531

When a customer, is also a worker, and replies to a ticket response from Helpdesk, the response says it was from the Helpdesk instead of from the customer. "For me that poses a problem because a ticket sent from a worker who is only in the Corp-IT group to the Facilities group won't behave the same way as a conversation between a regular customer and the same group but it should."

Steps:
1) Send a customer e-mail into the Helpdesk from the e-mail address used by one of your workers (i.e their login).
2) Have any worker reply to the ticket.
3) Have "customer" reply back to the Helpdesk.

Result:
When the reply gets processed, instead of it saying the customer submitted the reply, it says the Helpdesk did.


 All   Comments   Work Log   Change History      Sort Order:
Comment by Joe Geck [WGM] [14/Aug/08 07:42 PM]
http://www.cerb4.com/forums/showthread.php?t=1159

I know these scenarios are different but I think the solution of figuring out to treat worker addresses (registered with the Helpdesk) the same as regular addresses would solve all these types of issues.

Hildy [WGM] acknowledged in the thread that this is the root cause, so it sounds logical to assume the situation transcribed below would be "fixed by removal" so to speak.

[[Quoted from thread]]

Team A can only access tickets in their group.

Team B can only access their tickets.

2 people in Team C can only access their tickets, and 2 people in team C are the only people who are on Team D.


Let's say someone from Team C (me) sends a ticket to Team A through external email to Cerberus (not logging a message and assigning it to that team). Team A sends me back a reply (setting the ticket as Waiting automatically). When I respond back to Team A - the response is copied back to my own mailbox, and the ticket remains in "Waiting" status.

This also happened when someone from Team B used external mail to generate a ticket for Team C: Replied copied to the senders mailbox (Cerberus not set to do this from what I can tell) and the ticket does not shift from Waiting to Not Waiting.

Comment by Mike Ellis [18/Aug/08 03:46 PM]
This is a very important part of the system. I am in a very similar situation where "Customers" of Team A are "Workers" in Team B, causing tickets sent to Team A not to be re-opened on a reply from worker in Team B. This is causing a lot of problems between the 2 teams and a break in communication. In my opinion, this bug needs to be fixed a bit sooner than "wishlist" please and thank you.

Side note: Workers used to be able to reply and re-open tickets through email. As a temporary fix, what revision was this last seen? I believe it was somewhere after build 600, about the same time the INBOUND and OUTBOUND color coding.

Thanks,
-Mike

Comment by Joe Geck [WGM] [17/Sep/08 01:51 PM]
Moved to Milestone #20. There may be increased interest from a recent blog post.

Comment by Mike Ellis [29/Oct/08 06:17 AM]
Sorry to bother again but can we bump this up. It is very annoying to have to manually search for and re-open tickets replied to by workers through email. I'm sure there are others that would agree.

Comment by Stephen Bock [13/Nov/08 03:06 PM]
I hoped this wouldn't be pushed to the back-burner, but it looks like that's the case. I think this is a more important issue that what you guys think. The ability to treat workers as customers is extremely important when you have multiple groups in one organization. I hope this gets bumped up.