Unmet demand figure only appear to look at first task with under allocation

[ajerrison-manchester]

On the Available Projects page there is a useful 'unmet demand' number to give RSEs an idea of how much resource is needed for a project. This number doesn't appear to be correct though. It does not sum the unmet demand for all tasks, but appears to just look at the demand for the first such task.

A current example is RTP-477, which has two tasks of 0.4 FTE each, so 0.8 in total, however the available projects page only shows the unmet demand as 0.4.

[aharwood2]

I'm not convinced this is a bug, it is just not what you expect. I believe the number looks at the size of the "assignments". The largest assignment available is 0.4 FTE if you have two projects at 0.4 FTE then sure, the total is 0.8 FTE but it sees the maximum available assignment you are "advertising" is 0.4 FTE. Perhaps you want here is the peak Unmet Demand in the window alongside the range of unmet assignments. Given they are the same length, why did you add two separate tasks? Why didn't you just put one task with a demand of 0.8 FTE?

[ajerrison-manchester]

It just seems more logical and flexible to me to have one task per person, especially in such a long project. Given the amount of faffing about we have to do with allocations it is inevitable that in the future I'll have to split tasks for various reasons, or shorten one task and allocate someone else etc. There was already a question about whether one of the tasks might be for only 12 months for instance (depending on budget they think they can get). I don't think I've ever had a project where I have been able to sustain a task with 2 developers all the way from start to the end. :-)