GNOME Bugzilla – Bug 228174
Wishlist - Phone Message
Last modified: 2006-05-30 14:23:34 UTC
I have been asked to put in a request for one feature that is used very heavily by our current Groupwise 4.1 users (which is our 'live' email system and is going away in favor of Evo). They have the ability to send Phone Messages to other uses. It's basically a modified email message and shows up in your in-box with a telephone symbol next to it. It replaces those old pink slips that people used to fill out years ago. We have a very high number of users that receive phone messages this way (fire fighters and police officers). I don't even know how this would fit into modern technology, because the messages are delivered to multiple post offices rather than a proprietary GroupWise one. Anyway, here is the screen shot, activate by "New-->Phone Message" in GroupWise. http://www.largo.com/ximian/groupwise_phone.gif
Maybe I'm missing something here, but why don't you just send an e-mail with the subject "Phone message"?
Our communications area gets hundreds of phone calls a day that they enter into the system and send them to our police officers. Currently the screen looks exactly like those pink slips for phone messages. They can go in, click a few radio buttons ("Call Back", etc) put the phone number in and send it off. Phone messages could have their own folder then and one could click into that folder to just check phone messages only. I personally don't use this feature, but we have a lot of people that do.
changing component to "Mailer" to get rid of the UI component, also reassigning as discussed with nags... adding UI keyword. could also be "misc", though. but since it seems to depend on email... :-/
This issue is very old, but actually even more interesting now that there is a GroupWise backend for Evolution. Does GW 7 even support those phone messages anymore? If so, what does Evolution do with them?
Reguesting target version. 2.8? That would allow Evolution to receive phone messages created with the other GW clients.
*** This bug has been marked as a duplicate of 201428 ***