B
btrippindacap
Hi,
In project server 2003 the task view (assignments) was broken down
into a hierarchal view based on its parent outline task, etc. In 2007
this is not the case, it is all flat based on the project they are
contained in. Why is this the case and is there a way to get the 2003
view in 2007? It is all WSS so why can't I edited the view to put
grouping on it as you can in everything else with SharePoint. I have
ready some articles that you can achieve this with the schedule view
but after reviewing it is not even close to the 2003 view.
One of the main reasons is that task assignment names can be the same
(something like "Test Backup") under different parent tasks, e.g.
repeatable efforts. The problem that arises with this is that when a
user who is assigned to both of these tasks could see both of these in
their task view. This can lead to confusion and result in the user
entering time for the wrong task and then having to back it all out.
The only way the user can see is to click on the task to see the
details and view the path.
Aside from this question, does anyone have any good best practices for
2007 as a lot of my 2003 ones have changed.
Thanks,
n8
In project server 2003 the task view (assignments) was broken down
into a hierarchal view based on its parent outline task, etc. In 2007
this is not the case, it is all flat based on the project they are
contained in. Why is this the case and is there a way to get the 2003
view in 2007? It is all WSS so why can't I edited the view to put
grouping on it as you can in everything else with SharePoint. I have
ready some articles that you can achieve this with the schedule view
but after reviewing it is not even close to the 2003 view.
One of the main reasons is that task assignment names can be the same
(something like "Test Backup") under different parent tasks, e.g.
repeatable efforts. The problem that arises with this is that when a
user who is assigned to both of these tasks could see both of these in
their task view. This can lead to confusion and result in the user
entering time for the wrong task and then having to back it all out.
The only way the user can see is to click on the task to see the
details and view the path.
Aside from this question, does anyone have any good best practices for
2007 as a lot of my 2003 ones have changed.
Thanks,
n8