We want to programmatically change the Enterprise Project Type in Project Server 2016/Project Online as it was possible in Project Server 2013 with SubmitStage. Please add support in CSOM for this operation as it was available in PSI.

It should be possible to import national holidays into Project calendar, the same way we do it on Outlook.

Submitted on behalf of a client.

Similar to task notifications, allow for timesheet notifications in Manage My Alerts and Reminders with similar (appropriate) options.

There are currently no notifications to the Timesheet Manager when a timesheet is submitted. The only way to see this is by logging into Project Online and going to the Approvals page. This is not very user friendly and forces the user to "go see" if there are any new timesheets in the system to approve, rather than being informed that there is.

Long awaited integration between Project Online and VSTS. Would be good to have a story around agile frameworks like SAFe.

How is it not possible to have to separate Projects open at the same time, like any other Office product?

CSOM API for Engagements in Project Server 2016 on premise is missing.
Please add CSOM API or allow another way to update engagements programmatically.

The Engagements CSOM API works well for Project Online but fails when attempteing the exact same code on 16 On Premise (minus the authentication off course).
The error seems to be coming from the server:
“Microsoft.SharePoint.Client.ServerException: Field or property “Engagements” does not exist.
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponseStream(Stream responseStream)
at Microsoft.SharePoint.Client.ClientRequest.ProcessResponse()"

With the new Capacity Planning reports (Heat map, Resource utilization / availability etc.) there is no way to export the data to Excel like you could with the old Resource Availability view. Providing the functionality to Export to Excel will give the ability to do further data analysis. Also exporting to PDF would be good as the reports can easily be shared.

I propose to standardize the visualization as in Excel or Word, so to be able to separate the windows of 2 open projects in order to see them in 2 separate screens

The removal of HTML tags in the ODATA feed has had severe implications for custom reports which relied on these tags in order to preserve the formatting entered into Enterprise Custom fields displayed on PDPs. Is it possible to provide a way to select which fields in the ODATA field have the HTML tags removed, or failing this, to allow the admin to decide at Site Collection or PWA instance level.

Ensuring that key reporting tasks or milestones of a plan tempate is protected. This would allow for much stronger reporting and would remove the need of programmatically control specific key tasks.

Allow admins to create a custom list web part in the SharePoint project sites that can be included in the odata feed. This would allow for more effective reporting of project status in a narrative format. The existing solution (enterprise custom fields on a project detail page) does not save history and is littered with html tags in the odata feed. A custom list for status reports in the project site saves history but cannot be easily reported on across the system because it is not included in the odata feed.

Include the Status Manager in the tasks table in the Microsoft reporting database. Currently the only way is to go into each project to see the status manager. This would help in governance and support..

Change the way Projects are saved and published so the process takes less time and less requests.

Configuration and UI of Project Center, Resource Center views can be made more powerful. Especially searching projects/resources should be made much simpler and easier with keyword search not custom filter. Configuration should be made similar to SharePoint views. More complex filtering and [Me] and [Today] based dynamic filtering should be allowed. Filtering, sorting should allow some calculated functions from excel or vba etc. Formatting like conditional formatting should be introduced.

Analogous to the CSOM/REST API endpoints also the OData reporting endpoints should be security trimmed, providing only the data that is available to the user in Project Center and Resource Center