Quote:
Originally Posted by Greg Titus
So in order to support what we're talking about here we'd need some kind of additional store of information about resources that is outside of and in addition to the projects themselves.
|
Yes, I agree; that was what I was trying to get at when I mentioned that we need to be able to assign resources in a hierarchical manner. First, there is the overall availability of a resource, so that X% means that a resource is available only X% of his total available time. (Call this the Global Availability of Resource 1.) Second, there is the allocation to a specific project, so that a Y% allocation of Resource 1 to Project 1 means that, of the Global Availability, Y% is to be devoted to Project 1. (Call this the Project-1 Availability of Resource 1.) Third, there is the task assignment, so that Z% allocation of Resource 1 to Task A in Project 1, means that, of the Project-1 Availability of Resource 1, Z% is to be devoted to Task A.
The reason whpalmer4's attempt failed, I believe, is that, in Task 1.1, for example, Joe is listed at 50% of 100%, whereas it *should* be something like 50% of 50% of 100%. (ie, 100 Global availability, 50 of the 100 in Project 1, and all 50 of *that* 50 in Task 1.)
Unfortunately, I fear there is currently no way to do this in the current version of the application because the only granularity available is either Global Availability, or task assignment. But I'll be very happy to be proven wrong!
Question: If you keep one project per file (so that the resource's availability in the inspector corresponds to what I've called the Project Availability above), then could an Applescript gather different files, add up a Resource's availability and tell you what the Resource's Global Availability is?