Teams, Workflow & Labels
A team is a unit of work with its own board, for example Backend, Frontend or Design. A task always belongs to exactly one team. Each team decides for itself how its work flows, which labels it uses, who is on it and whether outsiders can see it.
Creating and arranging teams
Click + next to Teams in the sidebar.
| Field | Notes |
|---|---|
| Name | Shown in the sidebar and on the board |
| Identifier | The prefix of the team's task keys, such as BE in BE-14. It cannot be changed later |
| Starting workflow | The statuses the team begins with: the default four steps, a preset for design or product work, or a copy of another team's workflow |
| Private team | Off by default. Turn it on to make the team private from the moment it is created, so nobody outside it ever sees it. What a private team means is described under General: private teams below; the setting can be changed later there |
You are added to a team you create. The team appears in the sidebar with its Tasks, Projects and Views.
A team's menu in the sidebar, available to workspace admins, has Rename (name, icon and color), Move Up, Move Down and Delete. Deleting a team permanently deletes all of its tasks and cannot be undone.
Everything else about a team is in Settings → the team, on four tabs.
General: private teams
By default every member of the workspace can see every team's board. Turn on Private team to limit a team's work to its own members.
| For someone outside a private team | What happens |
|---|---|
| The team's board, tasks and activity | Not visible, including in search, My Work, Home and Insights |
| Discussions, files and documents that belong to the team's tasks | Not visible |
| A project the team shares with other teams | Visible, but the private team's tasks appear as Private task rows. They still count in the project's progress |
| A link to one of its tasks | Answers "not found", the same as for a task that does not exist |
| Workspace admins | No exception. An admin has to join the team to see its work |
Making a team private also settles the saved views of people who are not on it: their private views of that team are deleted, and their public views pass to a member of the team. The confirmation says so before you agree.
Turning Private team off makes the team visible to the whole workspace again.
Workflow: the team's statuses
A team's statuses are the columns of its board and the Status options on its tasks. They are arranged in three layers:
| Layer | Purpose | Required |
|---|---|---|
| Preprocessing | Definition, planning, refinement | Optional |
| Execution | The work itself | Yes |
| Postprocessing | Release, documentation, handoff | Optional |
Use Add step to create a status in a layer, and drag steps to reorder them. Each step has a name, an icon and color, and optionally a role.
Two roles matter to the rest of the product: Task Start marks the status at which work on a task begins, and Task Completion marks the one at which it is done. The Execution layer must contain both. Because reports, My Work and agents go by the role and not by the name, you can call your statuses whatever suits the team: rename "In Progress" to "Building" and nothing breaks.
Import… creates a workflow from a list of status names, for example when you bring a team over from another tool.
Labels
Labels are colored tags for a team's tasks: work type (Bug, Feature, Chore), component, or anything else the team sorts by. Each team has its own set.
On the Labels tab, Add label creates one with a name, a color and an optional description. Once defined, a label can be put on any task of the team and used to filter its board.
Members
The Members tab is the team's roster. Add member puts anyone from the workspace on the team; the change takes effect at once.
Anyone can remove themselves from a team. Removing someone else takes a workspace admin. When a person leaves a private team, their private views of it are deleted and their public views pass to a remaining member, because they could no longer open them.
Every change to the roster is recorded in the team's activity.
Priorities
Priorities are the same in every team and are not configured: Critical, High, Medium, Low, or none. See The Task in Detail.