Changelog

Every team reads a roadmap differently. Some want the columns running from Done back to Idea, and most have a status or two — Not Now, Idea — they would rather not stare at every day. The Roadmap’s columns now follow how your account works instead of the other way around.

What you can do

Set account-wide defaults in Settings → Statuses. Each tab — Outcomes, Opportunities & Solutions, Tests — now has a Roadmap card with two options. Reverse status order flips that view’s columns from last to first; for Opportunities & Solutions it flips the Combined view too. Default status visibility hides the statuses you toggle off from the Roadmap for everyone in the account, on the board and in the list view alike.

Adjust your own view from the Roadmap. The Display menu has a new Statuses section listing every status in the current view. Toggling one on or off only changes what you see — the account default stays in place for everyone else, and you can always bring a hidden column back for yourself.

See exactly what deleting a status touches. When you delete a status that cards still use, the reassignment dialog now leads with a warning showing how many cards across how many spaces hold it, so you know the size of the change before you pick a replacement.

Getting started

Open Settings → Statuses, pick a tab, and scroll to the Roadmap card. Any Admin or Editor can change the account defaults; everyone can tune their own view from the Roadmap’s Display menu. These settings apply to existing accounts immediately — until you change something, the Roadmap looks exactly as it does today.

For the full details, see the Roadmap documentation.

A roadmap gets hard to read once more than one group is working in it. Teams let you name the groups you actually work in — Product, Growth, Platform — and then use them everywhere the work shows up: on spaces, on cards, and as a filter on the roadmap.

Teams describe how your organization is structured, not what anyone can reach. They grant no permissions of their own — account roles still control access, exactly as before.

What you can do

Create teams in Settings → Teams. Give a team a name, a color, an icon and an optional description, then add people with the member picker. Anyone in the account can belong to a team, including Viewers, and one person can be on several teams.

Put teams on spaces. A space’s Leads and Contributors fields now accept teams as well as individual people. Assigning a team is a live reference rather than a copy: change the team’s roster and every space it is assigned to follows along automatically.

See the teams behind a card. Cards now have a Teams field in the detail sidebar. A card automatically carries the teams of the spaces it lives in — labelled with the space they came from — and you can tag an individual card with extra teams on top of those. Assignees are unchanged; they stay individual people.

Filter the roadmap by team. The roadmap toolbar has a teams filter, set to All teams by default. Check a team to narrow the board to the spaces that team leads or contributes to. The selection is stored in the URL, so you can bookmark your own team’s view of the roadmap or paste it into Slack and have it open the same way for everyone.

Getting started

Open Settings → Teams and add your first team. Accounts created from today onwards start with one team already named after your company; accounts that predate this release start with an empty list. Any Admin or Editor can create and manage teams — it is not restricted to Admins.

One thing worth knowing as you set up: while your account has exactly one team, people you invite join it automatically. As soon as there is a second team, the invite dialog asks which teams each new member should join.

Deleting a team never touches anyone’s account or access. Its members keep their accounts and their roles, and only the team’s own space and card assignments disappear.

For the full details, see the Teams documentation.