It may be worth noting that version 1.x and 2.x are no longer supported after February 2020.
Joining thread in case anybody else has any updates from MSFT on this.
We've never used these earlier versions, but in working on preparing 3.X for deployment I have encountered numerous bugs and currently have several tickets open with MSFT. These are being addressed, but unfortunately my report is that at this point, the 3.x documentation is lacking. Off the top of my head, here are some of the issues:
- The platform as a whole seems to lack workload management features for the lay user. IE it is great from the side of the PM, but there is no OOB "My Project Tasks View." We built that custom.
- No OOB way to mark project tasks complete. There are workarounds.
- Lacks workload management / reporting for resource teams. Queues could be used as one option. Assigning a team resource may work if booking the entire team and building a custom view for that team's tasks, but if trying allow a team to share a workload, but not book their entire capacity, see next point.
- Not clear if Resource Pools are supported. They are clearly a part of the resource scheduling solution, but we have not been able to add any resources to a pool. System either times out with a generic SQL error, or generates an error that the resource can't be a member of multiple groups (IE if the user is part of a team). Appears a user cannot be on both a team and in a pool simultaneously.
- Move project to custom date doesn't work.
- Can move project back, but not forward.
- Resource Utilization section shows only actuals. No apparent way to see booked utilization. For historic reporting, actuals are important, but for day to day determination of availabilty, given the delay between submitting and approval of hours, this is a hole. The documentation doesn't make it clear what the % on each resources label means.
- Gantt chart missing per above.
- No OOB way to enter hours on behalf of another user/team.
- No OOB syncing of user resources calendars into the scheduling board. MSFT indicates this is a design feature fore security / privacy, but even Free/Busy time or an option to let users choose to sync apts into the scheduling board would be very helpful. It is worth noting that apts and bookings are very different things within the system and the syncing options are limited.
Again, MSFT is working on the ones above that are generating errors, and we can build customizations for apparent holes in functionality, but to the point of this thread, where are the updates from MSFT? I notice occasional new additons to their documentation, but the 3.X documentation is far from complete. The release notes are posted by R. Hercules, the program manager, on a separate blog: https://cloudblogs.microsoft.com/dynamics365/it/2019/08/13/release-notes-for-project-service-automation-update-release-10/, rather than on the PSA documentation site.
