Hard to tell which public tasks belong to user

[skosner]

Maybe this is an oversight, but the following use of tasks seems to have serious limitations.

Let's say you organize a number of tasks in public folders to allow multiple users to collaborate on a number of projects. You dole out appropriate permissions to different users to the various folders/projects. So now, everyone can see and edit the projects in which they are involved. This all seems like a very typical use of tasks.

The problem is that, each user cannot easily tell, of which tasks in a given folder/project he is a participant. Consider a user that is involved in five collaborative projects that reside in five different public folders. In each folder there are about 50 tasks. Each task can belong to any other user(s) of that project. It seems he has to manually check all the tasks to see which belong to him. And repeat this every time he needs to check his to-do list.

Is there a way for the task interface to clearly indicate, of which tasks the user is a participant? So at a glance he knows which tasks belong to him, and also which other users are participants of those same tasks. This is, of course, in addition to looking at the complete task list and seeing how the project is progressing in general.

How else could this be effectively used as a collaborative tool? Is this an oversight, and there is a simple solution/answer, or is this functionality just missing?

Hope that's not an earful.

Thanks

Version : 6.16.0 Rev4 ( 2010-03-14 12:13:30 )

[Martin Heiland]

Hi,

right now there is no easy way to accomplish this use-case. The task module, especially for public folders, is not optimized for larger projects - more for single tasks. A satisfying solution would also include basic project management features like follow-up tasks, critical paths and so on.

A partner of ours has recently released a project management interface which integrates with data from Open-Xchange Server. http://www.sourcegarden.de/projectsimple.html

You could also report a feature request through Bugzilla or your account manager.

Greetings

[skosner]

Ok. Yes, a full solution would be a good deal of work. But at this point, just a single flag on each task indicating to the user that he is / is not a participant, would be adequate and make public tasks fit for collaborative projects.

Feature requests are filed along with bugs?
What is an "account manager"?

Sourcegarden does not seem to indicate any localization for english, but thanks for the tip.

Thank you

[Martin Heiland]

Hi,

you can file feature requests as bugs, we'll take them over to our internal feature planing tool. Account managers are sales/service people at OX that are assigned to customers, if you chose to get a commercial license.