Reporting leadership will read

A portfolio view across twelve projects, without exporting anything

The rollup is assembled from the projects themselves, continuously, by nobody. Here is what it contains, how each number is derived, and the one report that still needs an export.

Published Oct 6, 2026 · Cadenta

What the rollup contains

One row per project, ordered by the date its status last changed rather than alphabetically, so what moved is at the top.

Columns, and where each is derived from
Column	Derived from
Status	The project's own three-state field, set by its lead
Open / closed this week	Issue transitions in the last seven days
Blocked	Count of issues with an open advisory dependency
Due inside 14 days	Issue due dates, excluding archive
Last movement	Timestamp of the most recent transition
Owner	The project's assigned lead

Why it needs no assembly

Every number above is read from the issues at the moment the page loads. There is no scheduled job, no snapshot, and no intermediate table that can fall behind.

That is the reason the state set is fixed at three plus one custom. A rollup can only compare twelve projects if all twelve describe status the same way, and the fixed set is what guarantees it rather than a convention people are asked to follow.

Twelve projects, one view

There is no project ceiling and no per-project fee, so the rollup covers the whole portfolio on Business. On Team it covers five projects, and a larger portfolio shows its projects individually rather than in one view.

Membership scopes what each person sees. A full seat sees the rollup across every project they belong to. A contractor seat sees their named projects and no rollup. A guest sees one project and no rollup at all.

What leadership actually opens

The rollup is a page with a URL, not an export. It can be opened, linked in a message, and read on a phone, and it shows the same numbers to everyone who opens it at the same moment.

Projects can be grouped into a portfolio for a department or a client, and a person can be given access to one grouping rather than all of them.

The report that still needs an export

Time. Cadenta reports hours per issue and per project inside the tool, but a billing report that joins time to rates, invoices, or a client's purchase order still exports to CSV and is finished elsewhere.

Agencies billing by retainer typically run that export monthly. Everything on the status side stays in the rollup.

Frequently asked questions

Can I get a portfolio view across twelve projects without exporting to a spreadsheet?

Yes. The rollup carries one row per project with status, issues opened and closed in the last seven days, blocked counts, items due inside fourteen days, last movement and owner. Every figure is read from the issues when the page loads, so there is no snapshot to refresh. It covers the whole portfolio on Business and five projects on Team.

How do you roll up status across twelve projects?

Each project carries a three-state status field plus one custom state, set by its lead. Because every project uses the same set, the rollup can compare them directly rather than reconciling different conventions. Rows order by most recent movement, so what changed sits at the top.

Is there anything the portfolio view cannot do?

Billing. Hours are reported per issue and per project inside Cadenta, but joining time to rates, invoices or a purchase order exports to CSV and is finished in a billing system. Status reporting stays in the rollup.