It appears that a task "Owner" in TM Pro is the person who enters a task into the database. It there a way to reassign ownership, so a different person can be "responsible" for the task, even though the actual work is being done by other resources? Also, being able to assign the correct "Owner" allows for transparency, everyone knows who is ultimately responsible for the task.
We will add Supervisor option and Watchlist option to the next update. Supervisor option will let a User (supervisor) receive notifications of tasks assigned to a certain Resource. Watchlist will let a User to assign other Users to receive notifications of tasks they are not directly concerned with. If that will not work for your workflow, you will be able to use future feature Custom Fields for your purpose.
Modifying the ownership for a task is important to us because we frequently have team meetings where we discuss our projects. During these meetings, we have one team member acting as a scribe, taking notes and, now, assigning tasks. So, depending on who is logged in to Team Manager, that person becomes the owner of a wide variety of tasks, most of which have nothing to do with that person.
Our office dynamic is not particularly linear, I am not always the boss of Joe, and Joe is not always the boss of me. Having an inflexible supervisor model doesn't do us much good. What would work well is to have an assignable ownership field so that person is notified of a particular task's milestones, even though they are not the assigned resource.
Is there a way to create a custom field (call it Supervisor) that will:
1) utilize Task Manager users as the parameter to be chosen
2) allow notification of that user?
Hi Dave,
Well, now I understand your workflow however I don't quite understand why you need to change the owner.
If you need to receive notifications of tasks as a boss of a resource - you can use Watchlist feature (or you want to receive notifications of certain tasks assigned to this resource?)
What do you mean by "utilize Task Manager users as the parameter to be chosen"?
however I don't quite understand why you need to change the owner
Within our team we have the following situation.
A team member creates a task, but he's actually not responsible for this task. In order to that, the attribute "owner" for a task doesn't fit with all concequences (notifications, etc).
Quite similar to the problem described by Dave.
