we have something like this already in the backlog and will start to finalize the UX and implementation so it is inline with other features. Happy to say it is on the way and moving.
An error occurred while saving the commentAnonymous commented
We are doing something similar but using the Unassigned work feature to do this. We create different streams as unassigned categories.
then we add these to each project when creating them. That way we can schedule bookings in the demand categories and the supply are our teams. 1 step further we have groups which already represent each of these departments.
e.g. UX Group
Within the UX resource group we add the UX Unassigned category to that group as well. So when I want to schedule the UX demand I have all the UX people in 1 group and all the UX Project demand bookings and that way can schedule more clearly.
You can't add "budgets" to an unassigned category as they seem to be more generic than that and handle the supply and demand flow well.
not sure if this helps anyone.