Report: Time Allocation Matrix
Roll recorded time up through your work-item hierarchy or by persona, month by month, and export it to Excel.
On this page
Overview#
The Time Allocation Matrix answers a question the other time reports cannot: where did our effort actually go?
Other reports slice logged time by person or by item. This one rolls it up through your own hierarchy — your epics, your stories, your tasks, whatever structure you use — and spreads it across calendar months. The result is a grid you read top-down for structure and left-to-right for time.
It is built for the reporting people usually do in a spreadsheet at quarter end: how much went into each product line, how that split moved month to month, and what share of the total each branch consumed. Capitalization reporting, client billing summaries, R&D allocation, and "what did the team spend Q1 on" all fall out of the same report.
Open Measure Performance and pick Time Allocation Matrix under Time. It is gated by the same report permission as User Time Tracking (View the User Time Tracking and Time Allocation Matrix reports).
You choose the hierarchy
The rows are not fixed. You tell the report which item types to nest — for example Epic, then Story, then Task — and it builds the tree from your real items. A level can hold more than one item type, so a project team's stories and a help desk's tickets can sit side by side under the same parent. Change the levels and the same underlying time is re-cut a completely different way.
What you see#
The report runs in two stages: a setup form where you define the shape, then the results grid.
With Report rows → Item hierarchy, rows are your item hierarchy, one level per hierarchy level you configured, expandable and collapsible. A level that holds several item types lists their rows side by side under the parent, each row labelled with its own type, and the level's header joins the type names (Story / Ticket). Every parent branch also gets a subtotal row carrying its rolled-up hours and an allocation row expressing the same branch as percentages. A Grand total row stays pinned beneath the header as you scroll.
With Report rows → Persona, each row is a recorded persona, such as Engineer or QA Analyst. Monthly hours, monthly shares, total hours, and allocation show how the same scoped time divides between personas. Unspecified includes older time without a recorded persona; retired personas remain labeled. Each recorded hour appears once.
Columns are calendar months — Jan 2026, Feb 2026 — followed by Range Total and Total %.
Cells are logged hours to two decimal places. The metric is Actual Time: real time entries recorded against work items, not estimates.
Beneath the title you will see the run's provenance, for example:
Actual Time (hours) · America/New_York · Executed 11 Aug 2026, 09:14
Badges on rows#
| Badge | Meaning |
|---|---|
| Archived | The item is archived. Archived items are included — retiring an item does not erase the time spent on it. |
| Direct | Hours logged straight onto this item that no child row accounts for. Hover for the exact figure. |
Direct is worth understanding. If your levels are Epic → Story and somebody logged time on the epic itself rather than on any story, that time belongs to the epic and to no story. Rather than hide it or double-count it, the report keeps it on the epic's row and flags it. Direct where you did not expect it usually means work is being logged at the wrong level.
How to read it#
Down the Range Total column — how effort divided across your structure over the whole period. This is the allocation question: which product line, which epic, which client consumed the budget.
Across a row — how one branch's effort moved over time. This is the trend question: did the migration ramp up in March, did support load fall after the fix shipped.
The allocation rows turn the first reading into percentages automatically, both per-month and for the range, so you do not have to compute shares by hand.
Building a report#
Step 1 — Open it#
Click Measure Performance in the left sidebar, stay on the Analytics tab, and under Time in the report list click Time Allocation Matrix. Unlike the other reports this one does not run automatically — it needs a hierarchy before it has anything to show.
There is a keyboard shortcut
Press Cmd-K (or Ctrl-K) and type Report: Time Allocation Matrix to jump straight here from anywhere.
Step 2 — Set the reporting period#
Under Monthly reporting period, set Start date and End date. The defaults are the start of the current year through the end of the current month.
The helper text states the two rules:
Actual Time is grouped into calendar months in the organization timezone. A report can include up to 24 months.
Partial months. Columns are whole calendar months. If your start date is not the 1st, or your end date is not the last day of its month, that column covers only part of the month — and the report says so rather than quietly under-reporting. The header gains a suffix (Jan 2026 (Partial)) and a warning names exactly what was excluded: "Jan 2026 is partial; excluded Jan 1, 2026 through Jan 14, 2026 (14 days)." Only the first and last columns can ever be partial.
Pick whole months unless you have a reason not to
For allocation reporting, whole months compare cleanly and total correctly against payroll or invoicing periods. Use a partial range when you are looking at a specific window — a sprint, an incident, a client engagement — and want it bounded exactly.
Step 3 — Define the row hierarchy#
Choose Item hierarchy or Persona in Report rows. Configure the hierarchy below in either case: in the persona view it chooses which items contribute time, while the rows themselves show persona totals.
This is the part that shapes the report:
Levels are evaluated from top to bottom. Item type names stay current when they are renamed.
Level 1 — choose one or more Item types (say Epic), leave Selection mode on All, and set a Root scope with Choose items. The root scope is required when level 1 uses All, and it is what stops the report scanning your entire organization.
Level 2 onward — click Add level and choose the next item type or types (say Story). Levels below the first need no root scope; their items are found beneath the level above.
More than one item type on a level. Pick several types for one level when you want different kinds of work compared side by side under the same parent — a project team's Stories and a help desk's Tickets under one epic, for example, so one report covers both teams. Every type on the level must sit below at least one type on the level above, and the types sharing a level cannot be nested inside each other (if Task lives under Story, they belong on different levels, or an item under both would be listed twice). Each row is labelled with its own type; the level header and the export column join the type names, such as Story / Ticket.
Each level is a card with Move up, Move down, and Remove. Switching Selection mode to Selected lets you pick exact items instead — useful for a fixed comparison set, and those rows appear in the order you picked them.
Root scope is your main performance control
The report walks everything under the scopes you choose. A tight scope makes the report fast and readable; pointing it at your whole organization is the most common cause of hitting the 5,000-row cap.
The rules, which you will meet as validation messages:
| Rule | Message |
|---|---|
| At least one level | Add at least one hierarchy level. |
| No more than 15 | Use no more than 15 hierarchy levels. |
| Every level needs a type | Choose an available item type for level 2. |
| No more than 50 types on a level | Use no more than 50 item types on level 2. |
| No type used twice | Each hierarchy level must use different item types. |
| Each type below the level above | Task must be below Story or Ticket in the item-type hierarchy. |
| Types sharing a level cannot nest | Task sits below Story in the item-type hierarchy; level 2 cannot hold both. |
| Root scope when level 1 is All | Choose at least one root scope when the first level uses All. |
The hierarchy rule is the one that catches people. Levels must follow your organization's item-type hierarchy — Epic → Story → Task works, Task → Epic does not. They do not have to be adjacent: Epic → Task is fine if tasks live under stories, because the report looks for descendants at any depth. When the level above holds several types, each type only needs to sit below one of them.
Problems are listed under Complete the report configuration, and Run report stays disabled until they are resolved.
Step 4 — Run it#
Click Run report. Use Back to setup to change the configuration and Refresh to re-run it against current data.
Editing any setting clears the results
Changing a date, a level, or a selection invalidates the current results and returns you to setup — a grid that no longer matches the form above it is worse than no grid. Results also expire after 30 minutes, after which an amber banner offers Rerun report.
Step 5 — Read the results#
Start at the Grand total row pinned under the header, then collapse everything and read the top-level subtotals for the big split. Check Total % for each branch's share, expand the branch that surprises you, and repeat one level down.
Watch for Direct badges (time logged at a level where you expected it on children) and for warning banners — a partial period, or "Some configured selections are unavailable or outside the selected hierarchy." The latter means part of your configuration no longer resolves: an item was moved, archived out of scope, or you lost access to it.
If the grid is empty, the message distinguishes the two causes:
| Message | Meaning |
|---|---|
| No matching items — No authorized items matched this hierarchy and date range. | A configuration problem. Check the root scope and that your level item types match how items are actually structured. |
| No time recorded — Matching items were found, but they have no Actual Time in this date range. | A data problem. The structure is right; the hours are not there. |
Step 6 — Save it as a view#
Click Views in the toolbar and save. Choose Visible only to you or Visible to coworkers.
Saved views store the configuration, not the results — dates, row grouping, levels, item types, selections. Opening one drops you on the setup form with everything filled in; you press Run report for current numbers. That is what makes a monthly report repeatable. You can share a view by copying its link.
Saving and running use separate permissions
The form notes this: "Saving a view and running it use separate permissions." Saving needs stored-view permissions on top of the report permission, so you may be able to run a report you cannot save, or the reverse.
Views shared with you are filtered through your item access first. If a colleague's view references items you cannot read, those references are stripped and you get "Some saved report settings are unavailable or outdated." Re-pick the missing scope and run it. The stripping is deliberate — it stops a shared view disclosing items you are not allowed to see.
These views cannot be published to the customer portal; this is an internal reporting surface only.
Exporting to Excel#
The on-screen grid is for exploring; the export is for handing over — to finance, to a client, or into your own spreadsheet.
- Run the report first. Export stays disabled until there are results.
- Click Export, fill in Export Name in the Export Report to Excel dialog, and click Export Report. The name becomes the workbook title and the filename, so name it for whoever receives it — Q1 2026 Capitalization travels better than Time Allocation Matrix.
- DevStride takes you to the Exports tab of Measure Performance. When the job finishes, click its name to download the
.xlsx. It is not emailed.
What the workbook contains#
A single Allocation Matrix worksheet. For Item hierarchy, it contains:
- Row 1 — the export name.
- Row 2 — a provenance note: "Snapshot as of 11 Aug 2026, 09:14 America/New_York. Report timezone: America/New_York. Date range: Jan 1, 2026 through Mar 31, 2026. Metric: Actual Time (hours)." plus any warnings. This is why the export is safe to send onward — the recipient sees when it was taken, in which timezone, over what range, without asking.
- Row 3 — headers: one column per hierarchy level (a level with several item types is headed by their joined names), then one per month, then Range Total and Total %.
- Body — detail rows plus a subtotal and allocation row per parent, ending in Grand total.
Two deliberate differences from the screen: the workbook uses one column per level rather than a single indented column, so you can filter and pivot in Excel; and it contains every row, not just the expanded ones, with Excel outlining to collapse them.
Archived items get (Archived) appended. Direct time becomes an Excel cell comment on the Range Total cell. Hours format as 0.00 and percentages as 0.00% — real numbers, not text, so they calculate.
For Persona, the workbook has a Persona column, monthly hours, Total hours, and Allocation. A Monthly allocation row under each persona shows its monthly percentage shares. Retired personas and Unspecified remain included, followed by Grand total. It uses the same completed report as the screen.
The snapshot model#
Running the report creates a snapshot that lives for 30 minutes. The export renders from that snapshot rather than re-querying, so the workbook matches exactly what you saw — it cannot drift because someone logged time while the export ran.
The trade-off is expiry. Export too late and you get "Run the report again before exporting. The current results will remain visible until you rerun." Click Rerun report and export again; your results stay on screen meanwhile.
Item permissions are re-checked when the export runs, not only when you ran the report — so an export can never contain items you are not currently entitled to see.
Export while the numbers are fresh
If you are producing a report for someone else, run it and export it in the same sitting. The provenance row then carries a timestamp minutes old, which is exactly what a reviewer wants to see.
What is counted#
Time entries are included when all of these hold:
- The entry is completed — a timer still running is not counted until stopped.
- Its duration is greater than zero.
- Its start date falls inside your reporting range.
- It is on a work item inside your configured hierarchy that you have permission to read.
Everything is summed in whole seconds and rounded only for display, so a column can look off by a hundredth against a manual sum of the printed numbers. The underlying arithmetic is exact.
Positive manual subtask time is included too, against its parent item. Its completion date must fall inside the reporting period in the organization's timezone; an undated manual total is excluded. The same item-access and scope checks apply. Both row groupings count these records, including parents whose only time comes from subtasks.
Rows with no time are dropped
An item that matches your hierarchy but has no logged time in the range does not appear at all. The report shows where time went, not an inventory of everything that could have consumed it. An unexpectedly short report usually means the time was not logged, not that the items are missing.
Whose time? Everyone's. The matrix is not filtered by person — it sums all time logged against the items you can see, and there is no self-only mode. What limits you is item access: anything you cannot read silently drops out. Two people running the same saved report can therefore legitimately see different numbers.
How time gets in. The report reads completed DevStride time entries and dated manual subtask totals. Record time through the time controls, the item drawer's time-tracking tab, a timer, or the API. Workstreams organize the report's scope; time belongs to the work beneath them.
Which persona? The persona captured when the time was recorded. Later assignment changes, member-persona reordering, and persona retirement do not reclassify completed time. Switching from hierarchy rows to persona rows changes the breakdown, not the total for the same scope and dates.
Fixed choices#
Several things are deliberately not configurable, which keeps the report readable and comparable between runs:
| Metric | Actual Time (hours). No estimates, no points. |
| Column granularity | Calendar months. No daily, weekly, or quarterly view. |
| Timezone | Your organization's timezone, not the viewer's — so everyone sees the same month boundaries. |
| Filters | None. Scope comes from the hierarchy you configure, not from status, label, or assignee filters. |
Because the timezone is the organization's, the same report run in London and New York produces identical numbers. The timezone in use is printed under the title and in every export.
Limits#
| Limit | Value |
|---|---|
| Hierarchy levels | 15 |
| Item types on one level | 50 |
| Date range | 24 months |
| Rows in a result | 5,000 |
| Configured item selections | 5,000 |
Exceeding one produces a clear message asking you to narrow the scope. In practice the row cap is the one you meet, usually by putting a very granular item type at the deepest level across a wide scope.
Worked example: capitalization by product line#
Goal: how much engineering time went into each product line last quarter, split by month, as percentages.
- Period — 1 January to 31 March. Whole months, so no partial columns.
- Level 1 — item type Epic, mode All, root scope set to the Product Development workstream.
- Level 2 — item type Story, mode All.
- Run report.
- Collapse to level 1 and read the allocation rows for the per-month and range percentages per epic.
- Export for the finance team.
- Save the view as Quarterly capitalization, visible to coworkers, and re-run it next quarter with new dates.
Worked example: one report for the project team and the help desk#
Goal: one grid showing where the quarter's time went across projects and help-desk work, which live in different item types under the same epics.
- Period — the quarter, whole months.
- Level 1 — item type Epic, mode All, root scope set to the workstreams both teams work in.
- Level 2 — item types Story and Ticket together. Stories and tickets list side by side under each epic, each row labelled with its type, under a Story / Ticket header.
- Run report, then read each epic's allocation row for the split between the two kinds of work.
Troubleshooting#
| Problem | Likely cause |
|---|---|
| This report is too large to display | Over 5,000 rows. Narrow the root scope, drop the deepest level, or shorten the range. |
| Fewer rows than expected | Rows with zero hours are dropped. The items exist; the time was not logged. |
| The item-type hierarchy for level 2 contains a cycle | Your organization's item-type configuration has a loop. An administrator needs to fix it. |
| Time allocation matrix hierarchy cannot be resolved uniquely | An item is reachable by two different paths in your configuration. Simplify the scope so each item has one home. |
| Numbers differ from a colleague's | You have different item access. The report only sums items you can read. |
| Run the report again before exporting | The 30-minute snapshot expired. Click Rerun report. |
| Export shows Failed or Timed Out | Usually size. Narrow the scope or shorten the range and try again. |
| You no longer have access to run this report | The report permission was removed from your role. |
Related#
- User Time Tracking — the per-person view of the same underlying time.
- Reports Overview — the other reports and how exports work.