Task assignee

Gunnar Wrobel wrobel at horde.org
Mon Sep 12 08:14:54 CEST 2011


In the light of Bug 48 (Dropdown "Assignee" lists wrong persons [1]) I  
started asking myself a few questions on how the "organizer" field  
defined for tasks following the Kolab format should be used.

The problem: Horde allows you to select the "Assignee" ("Organizer")  
of a task. This works fine in SQL mode but turns out to be problematic  
with Kolab. The logic Horde uses to allow the selection of the  
organizer is to generate a list of people having access to a task  
list. Any of these can be selected as an "Assignee". Using Kolab as a  
backend this works fine for all users with admin rights on a task  
list. But of course you don't always hand out admin rights on a shared  
task list. If read/write is enough then there is no reason to provide  
more. But a user having only read/write access will not see the full  
list of potential assignees.

I don't know how other clients handle the same situation. My  
impression is that the Kolab format suggests using  
"organizers"/"attendees" in a similar way as they are being used for  
events. Here the organizer is always the event creator, cannot be  
selected and the sharing of the event happens via iTip (e-mail). Is  
this the intended mode for tasks as well?

Thanks for feedback!


[1] https://bugzilla.kolabsys.com/show_bug.cgi?id=48

Core Developer
The Horde Project

e: wrobel at horde.org
t: +49 700 6245 0000
w: http://www.horde.org

pgp: 9703 43BE
tweets: http://twitter.com/pardus_de
blog: http://log.pardus.de

More information about the format mailing list