B
Brian Hanks
Can the creator of a project set the “project owner†instead of only
defaulting to who creates the project?
It seems logical to me that if there is a function to take ownership of a
project, that there would be a function to assign ownership. Therefore when
our project coordinator creates the projects, she would be able to not only
set the PM, but set the ownership of the project to that PM, or someone else
if the case required. It could be as simple as identifying a step that we
don’t know about, or it might be a limitation within the application, I don’t
know, I am just asking the question.
Catch… the same should be asked about tasks within a project. If you can
take ownership of the Task, then it seems logical that you should be able to
assign ownership of the task. It also seems logical that unless a specific
owner is assigned to a task, then it seems it would default to the owner of
the project, not necessarily who created the task. This might be a setting
that says only the owner can add/remove tasks, or it might be another
limitation…It seems logical that you could restrict who can create tasks on a
project, just as you can restrict privileges within other apps. Again, just
asking the question…
Again, these might be limitations within project, and if so, so be it.
defaulting to who creates the project?
It seems logical to me that if there is a function to take ownership of a
project, that there would be a function to assign ownership. Therefore when
our project coordinator creates the projects, she would be able to not only
set the PM, but set the ownership of the project to that PM, or someone else
if the case required. It could be as simple as identifying a step that we
don’t know about, or it might be a limitation within the application, I don’t
know, I am just asking the question.
Catch… the same should be asked about tasks within a project. If you can
take ownership of the Task, then it seems logical that you should be able to
assign ownership of the task. It also seems logical that unless a specific
owner is assigned to a task, then it seems it would default to the owner of
the project, not necessarily who created the task. This might be a setting
that says only the owner can add/remove tasks, or it might be another
limitation…It seems logical that you could restrict who can create tasks on a
project, just as you can restrict privileges within other apps. Again, just
asking the question…
Again, these might be limitations within project, and if so, so be it.