Cut/Paste Finished Tasks

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)
 
M

Mike Glen

Hi Chris,

Try posting on the server newsgroup as this one's closing down. Please
see FAQ Item: 24. Project Newsgroups. FAQs, companion products and other
useful Project information can be seen at this web address:
http://project.mvps.org/faqs.htm

Mike Glen
Project MVP
 
G

Gary L. Chefetz [MVP]

DPROWJ:

Your instincts are on target. This is a very dangerous practice if they copy
at the row level. Copying task names, for instance, is not a problem. The
behavior, in general, indicates that nobody has taken the time to build
common workpath templates for your system.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top