I'd like to have a more auditable trace of changes to templates. We're currently writing release notes, but that's a bit manual. While we control access to templates and have changes go through a change control process, we can't systematically prevent another sys admin from enabling access they shou...

Our project plans are primarily structured to distinguish internal from billable work, yet our staff work on both. Tracking which hours are billable vs. nonbillable is a critical company metric, but the current system design leads to a potential error by the user in classifying the wrong hours. Rig...

There is currently no way to "bulk clear" multiple entry fields at the Project Level. Here's the example use case we ran into where this was needed - we needed to update the Resource Managers on a large number of projects, but the projects were originally configured very close to the 30-person limit...

If you create a Resource Pool by adding a team, group, or company it DOES NOT update the membership if you add members later to said team/group/company. Aka, in order to keep your Resource Pool up to date, you'd need to manually "refresh" it by either adding the new users individually or (i guess) r...

In case this is helpful for other folks: I originally thought that visibility into the Resource Planner was limited only if you had a Plan license and you were listed as a Resource Manager at the project level (aka, you can only see the projects that specifically had you listed as a Resource Manager...

Upvoted. Rather than increase the number of resource managers, I would also have a different way to configure this. Managing this at the user level by project is a bit of a nightmare for us - it leads to a lot of overhead when staff transition, as Resource Managers are often Team managers and resour...