D
DPROWJ
Some of my users, who work on big maintenance projects (which
technically never end) have started to cut completed tasks into other
projects which they use for record keeping, so for example:
Task 1 which was in project A, once completed, gets cut out of project
A and pasted into project finished_A. Is this a good Practice ? It
seems to me that the DB structure would not react well to such a move,
in fact is cutting/copying/pasting something that should be avoided all
together ?
If this is not a good practice, can anyone suggest a good way of
keeping track of completed tasks while keeping projects to a managable
size ?
Thanks
Chris
P.S. Set up on Project Server 2003(on Win Server 2003), using project
pro 2003 SP1(XP PRO SP2)
technically never end) have started to cut completed tasks into other
projects which they use for record keeping, so for example:
Task 1 which was in project A, once completed, gets cut out of project
A and pasted into project finished_A. Is this a good Practice ? It
seems to me that the DB structure would not react well to such a move,
in fact is cutting/copying/pasting something that should be avoided all
together ?
If this is not a good practice, can anyone suggest a good way of
keeping track of completed tasks while keeping projects to a managable
size ?
Thanks
Chris
P.S. Set up on Project Server 2003(on Win Server 2003), using project
pro 2003 SP1(XP PRO SP2)