Add configuration options for publishing projects
It would be appropriate that a configuration parameter allows or not to automatically publish a project after a status manager accept task updates on his approvals page. This would avoid to project manager to open and publish all project plans it has updated and ensure users of reporting that the published data are current.
Another alternative to satisfy this need would be to add a function in Database Administration section allows us to select one, several or all projects and force publishing (as for the function «Force Check-in Enterprise Object»)
I agree. The rule noted below to auto-publish is really auto-approve AND publish. I would like to see it where there the option to require approval but allow auto-publish once approved. Also, how about allow a rule for the PM to delegate another PM (or someone with the right permissions) to approve when they are traveling or out of the office?
A couple of options that we discovered to work around this:
(1) PMs can add a rule to auto-publish their projects. (The Manage Rules button is in the Approvals Menu Ribbon.)
(2) Also PM can select the History button (on the same ribbon menu) after approving the updates and select Status updates. Then they can select the ones to publish that were just approved (sort by the column to find them all if needed.)
Don't you wish this had been documented better?