Essentially in portfolio view, when using a custom percentage field as a measure of effort, that percentage shouldn’t be divided across duration of project. Aka if you’re 100% dedicated to a task, your daily total should be be 100% whether the task is 1 day or 5 days. Right now if you’re 100% allocated on a task for 5 days, the portfolio view says you’re only allocated 20% per day.
Not sure if this helps you since it’s a little different… we don’t use a percentage. We have an Hours Estimate number field. For every task, we enter the amount of hours planned to work on a task. If it’s assigned a due date, it allocates all of those hours against the date due. If it’s assigned a date range, it equally distributes the hours across the date range given, not the duration of the project. Then, under the Capacity, we list how many hours per person indicates 100% capacity.
That way, assuming 8 hour days and 40 hours weekly capacity…
- If I’m assigned a task to work on all week (date range) that will take a total of 20 hours, it will fill me at 50% capacity all week.
- If I’m assigned a task to work on all week (date range) that will take a total of 60 hours, I’ll show 50% over capacity.
- If I’m assigned a task with just a due date of Friday, I will show a big spike of over capacity by 32 hours on Friday.
So, in your example, to show 100% allocation across 5 days on one task, that task would have a due date of a date range of 5 days, and the Hours Estimate field would be set to 40 hours to max me out. Any other tasks assigned to me during that same 5 days would push me over capacity.
I’ll be curious to see what others say, though, since I’ve never tried it with a percentage field.
Hi @Alex_Lambert, thanks for providing this feedback!
While this feature isn’t available right now, hopefully it’s something our Product team can implement in the future.
I’ll keep you posted and let you know if we have any updates
I’m at Google and our teams are trying to track by % allocation and it doesn’t seem possible. Would REALLY like to see this feature supported ASAP. Thanks!
Seems like a very simple math tweak in the code.