LogoLogo
MethodsVisit our website
  • Overview
    • Getting started
    • Trends
    • Capacity
    • Allocation
    • Scenarios
    • Plans
    • Epics
    • Teams
  • Health Data
    • Cycle time
    • Flow efficiency
    • Intelligent forecast
    • Momentum
    • Resource contention
    • WIP limits
    • Dashboard
  • Additional Integrations
    • GitHub
    • GitLab (Cloud)
  • How to...
    • Add or remove users
    • Balance people's workloads
    • Change Jira project status configuration
  • OTHER RESOURCES
    • Data imported from source systems
    • Security
Powered by GitBook
On this page
  • View by historical trend or sortable table
  • Setting labor costs
  1. Overview

Allocation

Last updated 1 month ago

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 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).

For work time against an issue to appear in Allocation, the issue must have:

  1. An assignee (i.e., the ticket cannot have been unassigned);

  2. Time worked. Meaning, if an issue moves directly from backlog to done, with no time in an active status, it is not included in Allocation.

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 data is updated nightly.

View by historical trend or sortable table

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:

  • Parent entities (e.g. epics, or any other parent grouping levels you may use)

  • Jira project

  • Label

  • Issue type

  • Fix version

For any grouping, you can also see the allocation by person, and further filter by label or custom field:

You may optionally export the table to CSV using the icon in the lower-right of the table.

Regarding time allocation for labels and custom fields, note that:

  • Any labels assigned to a parent entity (e.g. an epic) are automatically inherited by the child 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.

  • If a label or enabled custom field doesn't appear in the filter for a particular time period, it's because we observed no worked time against issues with that label / custom field.

  • 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.

Setting labor costs

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:

  1. A default cost that applies to all contributors;

  2. 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.

Custom field. To see custom fields, you must first select them on the , under the Custom fields tab:

In trend view, you can filter any of these groupings to see allocation by person or .

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 any of the above options, as well as by .

Jira integration page
team
Team
software capitalization
Where to select the custom fields that will be shown on Allocation
Allocation table view shows the per-person distribution by grouping
Export allocation data to CSV
Assigning cost roles to contributors