Feature - Resource Allocation

Each day, LinearB determines which issues a developer actively worked on (issue activity or Git activity). The day is then divided equally across those issues.

Daily Allocation Example:
          Developer A works on 3 issues on Monday.
          
          Monday Allocation:
            Issue 1 → 1/3 day
            Issue 2 → 1/3 day
            Issue 3 → 1/3 day
            

Multiple active issues = equal split. Single active issue = full day to that issue.

Daily allocation is summed over the selected timeframe (week, month, quarter, etc.).

Weekly Example:
          Developer works on 5 initiatives every day for 7 days.
          
          Per day: 1/5 per initiative  
          Weekly total: 7/5 = 1.4 days per initiative  
          FTE Conversion: 1.4 / 7 = 0.2 FTE per initiative
            

FTE Formula: 30 days = 1 FTE

Allocation rolls upward:

• Issues → Epics
• Epics → Initiatives
• Initiatives → Portfolio themes (if applicable)

If work is done on a child issue, the parent receives that allocation.

An issue becomes “active” for the day if:

• It has an “In Progress” status with recent updates, or
• There was Git activity on the issue’s branch

Weekends count if work continues or if the issue remains active during that time.

You can view Resource Allocation by:

• Projects
• Issue Types (Jira)
• Work Item Types (Azure Boards)
• Initiatives (Jira)
• Epics
• Features (Azure Boards)
• Custom Fields (Jira)
• Fields (Azure Boards)
• Labels (Jira) / Tags (Azure Boards)

You can enable/disable breakdown fields using the Configure panel.

Shows overall allocation by category or field. Useful for understanding high-level distribution of engineering time.

Metrics included:

• Epics/Issues: count of active work items
• % of Total Work: proportion of total FTEs
• Effort (FTE): total FTEs for the timeframe
• Estimated Cost by FTE: uses average salary to estimate cost
• Issues With No Epics: highlights unlinked issues
• FTE Allocation by Issue Type: distribution across issue types

Displays every issue and epic contributing to a category with full traceability.

Breaks allocation down by team to show how each group contributes to the selected slice of work.

Visualizes shifts over time—helpful for understanding changes in priority, customer demand, or roadmap investment.

LinearB supports two types of saved filters:

• Project Filters – For well-defined projects with a specific business scope and delivery target.
• Filter Sets – For groups of activities without a fixed end date (for example, a product area, customer segment, or ongoing initiative).

Both can be applied to Resource Allocation to scope the dashboard to just that slice of work. Saved filters do not store a timeframe—they inherit the current timeframe from the module.

In Resource Allocation (and in Forecasting and Investment Strategy), the Project Filter menu is ont he top of the dashborrd next to + Add Fitler.

1. Set the filters on Resource Allocation to the scope you want.
2. Open the Project Filter menu and select Save Filter.
3. Enter a name, choose Project or Filter Set, and set visibility (Private/Public).
4. Click Save.

The filter is now available under View and Manage Filters and reusable across Resource Allocation, Forecasting, and Investment Strategy.

Click more at the top right of the dashboard. Use View and Manage Filters to see all filters you can access:

• Projects tab – Project filters, with Name, View (Public/Private), Target date, and Owner.
• Filter Sets tab – Grouped activity filters, with Name, View, and Owner.

Only the filter creator or a platform administrator can edit or delete a filter. If you see the Edit / Trash icons on hover, you have permission.

If you cannot edit a filter but want a variant:

• Open the filter, then use Duplicate Current Project from the Project Filter menu.
• Rename and adjust your copy, then save it with your own visibility settings.

To open the same scope in another module:

1. Open a Project Filter in Resource Allocation.
2. In the Filter Definition Area, click the Module Navigation Arrow.
3. Select Forecasting or Investment Strategy.

To share a filter:

1. Open the desired Project Filter.
2. Copy the URL from your browser’s address bar and send it to teammates.

Teammates must have access to the underlying module and data. Use Public visibility for shared “golden” filters you expect others to rely on.

Allocation is calculated per person, per issue, per day. For each developer-day:

1. Identify all active, assigned issues for that developer on that date.
2. Split the day equally across those issues (e.g., 3 issues → each gets 1/3 of a day).
3. Repeat for every day in the reporting period.

The unit is days and FTE, where 30 days = 1 FTE.

Yes. Allocation reflects where effort is attributed, not exact working hours. If an issue remains active and assigned through a weekend or holiday, those calendar days are included in the allocation.

An issue is active on a given day when:

• It is assigned to the developer, and
• It is in an In Progress–type state with recent activity (ticket updates inside a trailing window), or
• There is direct Git activity referencing the ticket (commits, branches, PRs) on that day.

FTE is a measure of total effort, not headcount. It is:

• Sum of allocated days across all contributors ÷ 30.

It is common to see more contributors than FTE because:

• People take vacations, holidays, and leaves.
• Some engineers work part-time.
• Developers split time across multiple initiatives, so each initiative only receives a fraction of their day.

• The in-app Resource Allocation dashboard refreshes daily at 6:30 AM UTC.

Subtasks roll into their parent issues:

• Assignment and activity on a subtask contributes to the parent story’s allocation.
• The parent rolls up further into epics, initiatives, or higher-level planning items.

Yes. There are two steps:

1. In the LinearB app, add the custom field in Resources → Allocation → Configure → + Custom field.
2. In the Cost Cap sheet, use the Setup and Classification by custom field tabs to map those values to capitalizable/non-cap logic or to groupings (e.g., investment strategy).

• No associated PM item
• Tags/labels missing
• Inactive or improperly linked epics

• Team has no active issues during the selected timeframe
• Developers not mapped correctly to teams

• Multiple initiatives remain active for long periods
• Parent issues misconfigured in PM tool
• Developers assigned to too many simultaneous issues