We use Workload as a core part of how we manage team capacity, and we’ve run into a significant gap when testing the new native Out of Office feature.
What we’re trying to do: Have a team member’s OOO periods automatically reduce their available capacity in Workload, so that task assignments and workload balancing reflect their actual availability.
What we’ve tried: When OOO dates are entered via a team member’s profile settings using the native feature, we expected those periods to appear as reduced or blocked capacity in Workload, the way a shaded unavailability block would. Our current workaround is maintaining a separate PTO tracking project, where OOO is logged as a task with start and end dates and hours. That method does surface in Workload correctly, but it requires duplicate effort.
What’s not working: OOO dates set through the native profile feature do not appear to reduce capacity in Workload at all. This means that if a team member sets their OOO natively, a manager looking at Workload would see no indication that person is unavailable, which creates a real risk of overassignment during that period.
For teams relying on Workload for capacity planning, this gap makes it difficult to adopt the native OOO feature with confidence. Connecting native OOO entries to Workload capacity would be a meaningful improvement and would likely unlock adoption for a lot of teams. Hoping others can weigh in, and would strongly support this being added to the roadmap.