Expand my Community achievements bar.

Subtract allocation and availability data when filtered out of Resource Planner

Avatar

Level 2

8/2/18

Current functionality: "Applying a filter does not change the allocation and availability data in the Resource Planner for projects, roles, or users. The filter changes only the amount of data that you see."

In order to use the Resource Planner as a resource budgeting tool, we need to be able to exclude the allocation data from projects when we filter out a particular status (such as Cancelled, Complete, Duplicate, we have a custom status called Below the Line - which means the project is not approved). It doesn't make sense to include allocation and availability data on projects in these statuses.

When we are resource planning a Portfolio we are not certain which projects will make it above or below our approved cut line. It ultimately comes down to capacity. Currently, in order to view where our capacity line resides in the Resource Planner, we have to manually remove budget data from projects with the Below the Line, Cancelled, Complete, Duplicate status. Based on the mix of projects we end up with, we may end up adding a project back in as approved (from Below the Line). Then we have to manually re-add the resource budget data. This is really problematic and creates a bunch of manual work/re-work.

5 Comments

Avatar

Level 1

8/9/18

Excellent idea.

Resource is not infinite in the real world and using Workfront to 'make the cut' makes it a far more powerful ally.

Avatar

Level 2

8/22/18

We are testing the new Resource Planning / Scheduling now and if we filter out projects, we really don't want their hours included. If this doesn't change I am not sure if my users will use this functionality.

I voted! Shannon, make sure you vote for your own idea too!

Avatar

Level 4

8/22/18

This is another very good suggestion for the new Resource Planning system. I has the making off a really good tool but it still lacks functionality like this.

Avatar

Level 1

8/23/18

Really problematic for us too. As Legacy Resource Grid will desappear soon, I really hope this will be corrected within the next 2018.3 release.