Have you ever been in a team meeting, made a bunch of updates to your project plan, and then wanted to know later which tasks you had actually updated? A coworker emailed me with this scenario today and I decided that the solution deserved a blog post.
There are 2 steps to this solution.
Step 1: In the meeting, before you start making updates to the project plan, insert the Flag1 column. (If you are already using this column, any flag field will do.) Then as you update a task, set the value to Yes.
Step 2: To now see all of the tasks that you have updated, go to Project - Filtered For: - More Filters - New. Name the new filter, Tasks that have Changed. Set the Field Name to Flag1, Test to equals, and Value to Yes. Click OK to save the filter. Now select the filter from the dialog and click Highlight. This, instead of filtering out the tasks where flag1 isn't set to yes (which would have happened if you had clicked Apply), just highlights the tasks where flag1 is yes so you can still see them in relation to the rest of the project plan.
You can use the highlight filter anywhere that you would use a regular filter. It is best used when you want to filter on a certain criteria but also want to be able to see the entire project plan.
Does this only work with MSProject 2007? We still have 2003 and I would love to be able to get this information.
This does work in 2003. You can follow the exact same steps that I describe above.
This has occured more than once in my experience. I started insertin the Flag1 column 2 years ago and have never missed updated tasks. But I like the flitering suggestion that sets Flag1 to "yes". This will be my next step which wil save a lot of time.
Thanks for your help.
This is a "good idea but..."
Just as Prj already contains "Date Created", it should also have a "Date Touched". This field would be updated whenever the task is modified directly (such as a change to the duration or a new resource assignment, etc.) but *also* whenever it is changed because of, for example, a change to a predecessor which, because of a predecessor/successor link, forced a change.
I know that it is possible to view the constraints (in P2007) that had an impact on scheduling a task but that's not really quite what I have in mind for a "post updating" review that we're talking about here.
This is awesome, you just saved me an hour out of my day trying to track changes. Thanks,
This is wonderful!
I really love it.
Wish MR.Heather O'Cull and yours all the best