Over Allocated in CVS version

[tshawkins]

I have just installed a clean version of cvs, and dont seem to be able to allocate resources, no matter how much allocation I provide, ie 30%, 50% etc it always pops up the "over allocated" box, even though the resource is showing 0% allocation. I also get the problem of only beinag able to see "admin" in the resource list.

[Wendebaum]

0% indicates that this "resource" has no free space anymore. The number indicates the amount the person still has left to be assigned.

[tshawkins]

Ahhh.ok, I take it admin has no allocation then, because with no tasks assigned its showing as 0%, can I suggest you add the word "free" to the end of the percentage.

I also cant seem to get any other resources other than admin to appear in this list, dispite creating new users, is there anything I have to do to a user to make them eligable as a resource?

[tshawkins]

second thought, would it not be better to display % allocated, so that if you allow overallocation it will display as 130% rather than (-30%) which would be confusing.

[tshawkins]

Ok, anwser my own question, the reason why I cant allocate new users as resources is becuase I had'nt assigned permissions yet.

[tshawkins]

perhaps the "default user preferences" should allow default permissions to be set.

[caseydk]

At the same time a user is created, their permissions can be set by either defining them explicitly OR by copying from another person and then customizing as needed.

[tshawkins]

I have found one other problem with user allocation, looks like a bug of some sort... When I create a new user, even though I set the preferences to give them full permissions, they still appear as 0% available, untill I manualy edit thier preferences and set thier locale to "en", for some reason they are being defaulted to "cn" even though I have set the default user prefereneces to "en". Im not sure why the locale should effect availablity.

[tshawkins]

Ok, more digging, its ANY access to preferences enables the user.

To reproduce,

1. create a project and a task
2. creat a user, and assign permissions for all, dont touch preferences.
3. go to the task and try to assign, overallocated !!!!
4. goto to user management, select the user and edit preferences
5. Dont change anything, just press submit
6. Return to task, and user can now be allocated.

There is something in the preferences update code that "allows" a user to be allocated.

[jcgonz]

There is one issue that I would like to understand:

Example:
- I have one task for today that I allocate 100%
-> It will take me all day
- I have one task for tomorrow, that will also take me all day (100%)

The current CVS version will not enable me to create the second task because I'm allready 100% allocated (0% free).

The issue here is that I might have a task that needs to be done within next year, and I will not be able to assign it to me (plan) because now (not next year) I'm overallocated.

How am I suppose to solve this problem?

[caseydk]

tshawkins... I'll play around with this and see what I can come up with.

Thanks for the detailed steps to reproduce it.

[cyberhorse]

the problem pointed out by jcgonz I think is very important and urgent. Without this, the overallocation is meaningless, because sooner or later most users will reach 100% and if time is not taken into consideration, the whole thing becomes meaningless. As such, I believe tasks that have no dates should probably be ignored by the allocation percentage code.

[tshawkins]

I would like to suggest the following.

1) Drop the "blocking" overallocation check, as a PM I would tend to data-enter a project, allocate resources, and then go back and fix up afterwards, the current "blocking" system forces me to deal with resource leveling at that point, where I may not have all the info available.
2) Change the indicators to show allocation, not availability, hence a user could show as 130% if overallocated.
3) add filter option to the resource utilisation reports to report overallocated resources only.

[Wendebaum]

yep, sounds good... :)

[caseydk]

As long as it is *clearly* marked after someone is over allocated...

Maybe dump the allocation check but show what their allocation is on the assignment screen(s):

caseydk [1250%]

[jcgonz]

Actually I suggest to show the overallocation warning in the status var (window.status) and allowing the user to be overallocated.

I really hope this hole issue can be solved ASAP, it has been very problematic with all my users.

[r.ghizzi]

sorry for that silly question :oops:
when the user allocated percentage is freed?
i cannot understand