I would like to create a task container system for organizational purposes i.e. have subtasks grouped together. The root or container task doesn't need an owner or status as it isn't really a task just. I was hopping to create a user team or group and assign ownership to that so we can have simple criteria for our task smart lists that filter all tasks owned by "me" or my team.

The work around I guess is to create a dummy user that represents the team and assign these tasks to that user. But this seems wrong as there is a notion of a user grouping.

The reason I want to do this is two fold:

1. I want to create an organization tree of subtasks that is common to everyone. They should be able to see the tree and their particular subtasks assigned to them.

2. I want to have tasks that anyone on the team can grab and assign to themselves. These would be the equivalent of unassigned tasks.

Is there a reason why teams can't be the owner of something?

This message has been edited. Last edited by: Andrew Migliore,