The Resource allocation page is available in the General pane under Planning.
It gives you the ability to view the workload for individual users and also see if they are under- or over-allocated.
When is an task/issue visible in the Resource allocation?
For an issue to be visible these are the constraints:
1. The task/activity has a Start date and a Due date set - "Estimated time" will be counted from Start and Due, that is, 100% work on the issue is expected.
2. The task/activity has a Start date and an Estimated time set.
3. The task/activity has a Due date and an Estimated time set.
4. The task/activity are planned for an iteration/sprint/phase (version above) and it has a Start date or a Release date and the task/activity has an Estimated time
In alternative 4.) above, the task order in the iteration/sprint are ordered based upon the "Global rank field" (if that is used) otherwise according to "priority".
How are issues "distributed" or spread out in the grid above?
Issues that is added "because of" point 1., 2. or 3. above will always be added using the dates even if this means that a user can be over-allocated.
Issues added "because of" point 4. above will be added where it "fits". i.e say that you have these issues:
Issue 1 - Start date: 2012-08-01, Due date 2012-08-03, No iteration/sprint/phase, No est. time
Issue 2 - No Start date, No Due date, iteration/sprint/phase that starts on 2012-08-01, Est time = 16.
Issue 1 will be placed on 2012-08-01 to 2012-08-03
Issue 2 will be placed on 2012-08-04 to 2012-08-05 (because if it would be placed on 2012-08-01 to 2012-08-02 the user would be over-allocated.)
If a user has "availability" set on the iteration/sprint/phase then the issues that the user has for that iteration/sprint/phase will be distributed on those week(s).
How are Free time, Overallocated, etc calculated?
Free time, Balanced, and Overallocated are shown using colors in the grid.
When calculating the allocation for a user, this is the "rules":
Allocation on the User-level
For each day the total hours of allocated time is summed up to the user. That total is then compared to the available time in the "Work schedule" that is specified on the user.
Note: For the "Unassigned" user (Used for issues with allocated time, but no user set to Developer or Owner), the first Work Schedule in the settings are used (See General > Settings >SLA Settings > Work Schedules).
Allocation on the Project-level
For each day the total hours of allocated time for that project is summed up to the project. That total is then compared to the "Project availability" that is specified on the project for the specified user.
Allocation on the iteration/sprint/phase (version)-level
For each day the total hours of allocated time for that iteration/sprint/phase is summed up to the iteration/sprint/phase. That total is then compared to the "iteration/sprint/phase availability" that is specified on the project for the specified user.