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.
If the projects you are trying to check in or publish appear to be stuck, something may be blocking the queue. The first step to resolving this issue is to look for projects in the Getting queued state.
To view the jobs currently in the queue, click Server Settings on the Quick Launch in Project Web Access, and then click Manage Queue on the Server Settings page. If the list of jobs is long, you may find it helpful to filter the list of jobs by status, looking for jobs in the Getting queued state.
When reviewing jobs in the Getting queued state, don't forget that some actions, such as checking in a very large project over a slow connection, may take quite a while to process. Before proceeding with the next step, be sure that the job is actually blocking the queue and not just processing slowly.
Once you've identified the job that is blocking the queue, the next step is to cancel the job. By default, jobs in the Getting queued state are protected from being canceled. You can turn off this option, but be very careful when choosing what you cancel. When you cancel a job in the Getting queued state, you will lose any changes you made since the last time you checked the project in.
If you are sure that you want to cancel the blocking job, in the Advanced Options section, select the Cancel jobs getting enqueued option. Then, select the job that is blocking the queue in the Jobs Grid, and click Cancel Job.
With the blocking job now canceled, the queue should resume processing subsequent jobs.
For more information on queuing in Microsoft Office Project 2007, take a look at the following:
· Microsoft Office Project Server 2007 Queuing System
· Managing jobs (events) in the Project Server Queue
TechED 2008 - Developers and TechEd 2008 - IT Professionals are two months away!
Please find below the EPM sessions that will be delivered at these events:
TechED 2008 - Developers
TechEd 2008 - IT Professionals