Skip to main content

Above a single project

Portfolio and enterprise views above the project

One project is a board. Four related projects are a portfolio. Everything the company has running is the enterprise view — the same work, at three altitudes.

Three levels, one set of issues

Each item below is functionality in the product today.

Portfolio profile

A portfolio is a first-class record with its own profile, documents and discussion, not just a filter on a project list.

Portfolio backlog and board

See and plan the work of every project in the portfolio together, using the same board and backlog you already know.

Enterprise backlog and board

The same view across the whole company, for whoever needs to see everything at once.

Projects belong to a portfolio

A project carries its portfolio, so the grouping is a property of the work rather than a saved search someone has to maintain.

Mentions and discussion at portfolio level

Comment on a portfolio profile and mention people the same way you would on a project, with the same email notification.

Permissions per level

Portfolio and enterprise views are separate permissions, so seeing everything is something you grant deliberately.

Why the levels are separate permissions

The enterprise board is a genuinely different kind of access: it shows work from projects a person may have no access to individually. Making it its own permission means the decision to grant a company-wide view is explicit rather than a side effect of a role someone was given for another reason.

One set of issues, three windows

Nothing is duplicated at portfolio or enterprise level. These are views over the same issues, with the same keys and the same history, which is why an issue moved on the enterprise board is moved everywhere.

Related

Or go back to all features.

Try it against your own work

A workspace takes a couple of minutes to create. Put one real project in it and see whether this shape matches how your team already works.