Who are tasks assigned to in Chandler?

Jeffrey Harris <[email protected]>
Newsgroups gmane.org.osaf.design
Message-ID <[email protected]>
Hi Folks,

Recently on the design list Mimi mentioned that we'd like to encourage
users to use the message stamp To field as task-assigned-to.  I've been
trying to sell this to people.  After discussing it with folks who split
up tasks in small work groups constantly and want to track who a task is
assigned to, I'm beginning to question if the message-stamp is adequate
for assigning tasks.

First, I don't think it's immediately obvious that a mailed task's To:
field is intended to convey that someone has taken responsibility for a
task, it might help to just render the To: field's label as
"Assigned-to" instead of as "To" for message-tasks.

Second, what about items that started out as emails?  For instance,
suppose a small group of people are jointly coordinating responses to
emails.  If email could be marked as tasks and contacts could be added
to a separate assigned-to attribute, I think this would be quite doable,
as it is now, changing the To: seems really confusing.

Sincerely,
Jeffrey

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

Open Source Applications Foundation "Design" mailing list
http://lists.osafoundation.org/mailman/listinfo/design
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.