PS2010: Auto-Approval Status Update strange behavior (skipped for optimization) RRS feed

  • Question

  • Hi everybody,

    Project Server 2010: In a customer installation we have set auto-approval rules for all project managers. The "auto-publish" flag is enabled, so the changes submitted by the team members are automatically propagates into the published version of the plan. 

    What we have noticed is that, when the Project Manager has the plan checked out during the status update, then the change does not pass into the plan (the queue job shows a 'skipped for optimization' state). That's expected. What is weird is that, upon checking in the project plan,the change that was previously submitted from the team member (and skipped) (let's say % work completion update) is passed into the Draft version of the plan, WITHOUT  being published, which is very confusing for the users, because you end up seeing 2 different forms the same task (draft and published) without an actual feedback as to when or why it occurs.

    So, it seems that the status update works, but the auto-publish rule does not work as expected in this scenario. Why is this happening? Do you know if this behavior is corrected in a certain CU?



    Friday, March 22, 2013 11:35 AM

All replies

  • Spyros,

    No, behavior is as expected, updates will first go to draft and project manager has to publish the project plan to update published data and eventually reporting database.

    Also publishing via PSI or PWA is considered as partial publish and publishing via Project Pro is considered as full publish.

    Hrishi Deshpande – Senior Consultant DeltaBahn
    Blog | < | LinkedIn

    Please click Mark As Answer; if a post solves your problem or Vote As Helpful if a post has been useful to you.This can be beneficial to other community members reading the thread.

    Friday, March 22, 2013 4:14 PM
  • thanks for the reply.

    I'm still a little bit confused though. In SP1 the option "Automatically publish the updates" was added, that is supposed to publish the project once checked in. So, why do the updates in our case go only to draft?

    (Keep in mind that if the project is not checked out when the rule runs, the auto publish takes place normally)

    Saturday, March 23, 2013 12:16 PM