787 Views
10 Replies
Last post:
Dec 19, 2008 11:15 AM by
Vinh 
Hi Dan,
But I can also appreciate the challenge of convincing Ceo's, Cfo's and the like of adopting new work/communication practices.. Especially when it calls for them to
A: move away from from a process they know and trust
B: adopt new tools and concepts
... The twin road blocks to change..
I don't envy your position 
Either way.. Good luck..
Cheers
Nathan
I agree that what should be happening is that users should be moving their conversations to the Web and getting off of email.
The problem is that Clearspace goes half way and it makes for a confucsing user experience.
Check out the screenshot of an email notification sent via Clearspace. The email was triggered when I thread I was watching had a new post in it. The post was made by Mike Peters. (This is one email notification use case in Clearspace. There are other examples where something similar is happening)
So the email notification I got says that it is from Mike Peters. But upon closer examination, the from address is not Mike's. It is set to the system email address I configured (in this example that address is barnyard2-donotreply@stanford.edu)
So it "appears" that the email is from Mike, but really it is not. And if had the option in email client configured to only show the display name and not the email address, then I would be further mislead. You can see how a user might easily reply to the email and think he was sending something to Mike.
It just doesnt make sense that clearspace would use the post author's real name in the notification, but not the persons real email address. Instead it mixes the two. At the very least remove the persons real name out of the From field so that peoples names arent being associated with a bogus email address. Is there a way to do that?
YES, thank you for explaining our issue in a clear manner 
Really, the two major items we are running into with Clearspace is:
1. This issue as described
2. Project Management enhancements
Loading related product issues for this case
To better serve our customers we have included functionality to automatically follow up on a case after it has been idle for more than 5 days, and then auto close after an additional 3 days of inactivity. Choose No to acknowledge that this case will remain idle for longer than 5 days.
Making cases public allows other customers to learn from the solution of the case. It can also be used to gain feedback from others in the community. Ask our Support Engineers for more info, but we encourage you to make your cases public.