This is a good idea, and needs to be a separate permission as the only way at the moment is to open all access to do all booking to any engagement.
a really clean bulk output format as well. capture of time in HubPlanner that needs to go into other systems at week/month end
If the screens could also update after this that would be great. A bit annoying when adding new unassigned work categories to a project, you have to go through a whole screen manual refresh.
This would be fantastic to have under project details and resource details a change log. I would think that there would need to be some design thought so it was not just a server log (with 1000's of rows), but tracing which user was last to update with, even if high-level on first pass of this functionality would be a good start:
Project settings changed
Resource details updated
Resource removed/added from project
We have added the days option to reports. Does that help?
I agree. Reports help, but days as a site wide preference on account settings would be better
I agree, setting future dated availability is good.
Current workarounds force dual handling:
1. set to non bookable and set custom hours. then remove these settings at start date.
2. Leave resource settings as standard working hours capacity, and put a not available booking in to reduce team capacity
Not elegant, and requires double handling, or more.
4 votesAnonymous shared this idea ·
Agree, a simple resource field of start date and end date would be really beneficial to capacity planning. Having too much capacity before start date, and having to time the exact data update for when the resource becomes available is not ideal for longer lead time planning.