Allocation
Last updated
Last updated
Allocation shows you the distribution of time worked for any period you select. It's useful for understanding how worked time aligns to company priorities.
Allocation is also valuable in accounting for software capitalization costs. With Allocation you can see, for any time period, the percentage of time invested by person and type of work (e.g. new development versus bug fix or maintenance).
To calculate time worked, we're interested only in issues that spent time in an active work status for the calendar period you select. If issues have worked time prior to the calendar period you select, we exclude that portion of worked time from the results.
For example, say you pick a calendar period of the past 14 days. We will show all time spent on issues that were active during that period. This includes both still-active issues, as well as any completed issues (provided the completed issues spent time in at least one active phase). Any time spent on those issues prior to the past 14 days (in this example) would not be included.
Allocation is updated nightly. For work against an issue to appear in Allocation, the issue must be assigned, with time worked.
Allocation has two view modes, trend and table.
In the trend view, we show the allocation of time spent for the period you select, and how that compares to the prior five equivalent periods. Click any of the bars to see its details in the table below. You can also select a bar segment to see the trend for just that segment of work.
You can see percentage of time spent, for any calendar period you choose, grouped by:
Epic
Project
Label
Issue type
Fix version
In trend view, you can filter any of these groupings to see allocation by person or team.
In the table view, we show the allocation of time spent for the period you select in sortable table format and organized by your chosen grouping. For the table view, you can group by:
Epic
Project
Label
Issue type
Fix version
For any grouping, you can also see the allocation by person:
You may optionally export the table to CSV using the icon in the lower-right of the table.
Regarding time allocation for labels, note that:
Any labels assigned to an epic are automatically inherited by that epic's issues. So, if an epic with the label of "Customer" has ten child issues, any work on those issues would appear against the "Customer" label in Allocation.
The time worked across labels may sum to greater than 100 percent. This is because issues may be assigned more than one label, in which case the total worked time for the issue is allocated to each label.
You may also optionally define labor costs to see, for example, how much money has been invested to-date in a given epic or type of work.
To set labor cost, click the Socratic (S) logo in the upper-right of the app and choose Cost. When setting labor cost, you have two options:
A default cost that applies to all contributors;
The creation of cost roles, which may then be assigned to contributors individually.
To assign cost roles to contributors, choose the People tab on the Settings page, and then choose the Contributors button:
If no cost role is assigned to a contributor, we use the default cost value.
