Resource Engagments would need better reporting (more columns in the odata feeds; for example EngagementComments) should be enable to better track and report your Resource Portfolio.

I can't display the calendar week numbers in my project timeline. From week 1 to week 52 each year.

Only "project week numbers" with prefix "W" are available, starting on the week where the project starts. The prefix "W" is not a mandatory need for displaying calendar week numbers.
It could instead be e.g. "CW" for calendar week. CW01, CW02, CW03....CW49, CW50, CW51, CW52, CW01, etc...

Eg. this week (from monday 18'th of april) has calendar week number 11. CW11.

Enable spelling and grammar check on PDPs, in particular for custom fields with multiple lines of text. Today you can select the spelling language in the Format Text ribbon, but it does not flag any typos. Having a spelling and grammar check on custom fields with a single line of text would be useful as well. Today the only option seems to be downloading and installing browser freeware.

The current #TaskPath feature will highlight predecessors and successors of a selected task, but when you have several hundred tasks and the successors are many lines below, it is difficult to follow the full task path. I would like to be able to #filter the predecessors and successors (and driving predecessors and driven successors) to get a quick look at all the dependent tasks.

I would like to have a chance to input comments (and/or notes) on the timesheet per day and not by task.

There are multiple options defined in two look-up tables. Instead of having all of the options available in field 2, the options are limited after the user chooses an option in field 1.

The Task entry shows a total hours by Task line but there is no Total for the entire Period. I don't know that Timesheets shows a period total but whether it does or not, it should also be available if a company opts to use Task Entry (versus Timesheets)

Allow admins to choose date or date/time format for new enterprise custom fields. Right now, all date fields are date/time, which is not intuitive for users.

Improve performance. The queue jobs are not moving...

Possibility to manage something like SharePoint lists or managed metadata to improve lookup table maintenance (e.g. Customer list from LOB).

e.g. when Suzie leaves the company, allow for a global replacement of status manager on any tasks that carry her name. OR when a Chris has an accident and never returns to work, allow any timesheets that have already been submitted to him but not approved to automatically transition to the new assigned timesheet approver.

For some key business reasons, we do not use the Timesheet function. However, we would like the ability to know when Task Updates are submitted for weekly periods to be included in the oData so that we can report on submission (versus having to wait for approval from the Status Managers.)

It would be very helpful In the timescale set up options when you select "Use fiscal year" that "FY" is added to the date display. So that the 2016, 2017, 2018 is shown as FY2016, FY2017, FY2018 or FY16, FY17, FY18 in the label. So that the viewer or reader visually knows the schedule calculated by FY, vice CY years. Many government programs must use fiscal year so "first quarter" is Oct - Dec.

Steve

The time period shown on the screen should be based on current date. For example, this is Dec. 16, yet a period for August shows on the screen. I have submitted a timesheet for August several times, only to have to back it out. Instead, I have to search for current period each time for data entry. Also, I send my timesheet to same person every week, yet I have to search for the name because the default name is first on the list. Again, I have had to back out.

Allow administrative configuration to show or hide command buttons, as dictated by organizational needs. Many buttons aren't ever needed by us. The current 'solution' of simply hiding toolbars only confuses or frustrates our users.

When creating a Risk you have the option to assign a risk to another person. Although you assign a risk, it does not notify the person assigned unless the risk is manually shared once saved.

Ideally the risk should be automatically emailed to the assigned person upon saving the risk

You logged your Risk, now its an issue, with one click it creates an issue...you fill out the rest of the details and it links back to issue, date and history with it. This proves a PM did his due dilegance early on in identifying risks as well. Every time I train customers someone always asks if they can do it, I have to say sorry no easy button.