Projects

A project is a container with its own members, states, labels, estimates and settings. Tasks live in exactly one project, and the project decides who can see them. This page covers creating one, what it starts with, who can see it, and the per-project switches that decide which tabs appear.

Creating one

New project on the Projects page asks for four things:

  • Project name.
  • Identifier, the prefix on every task key. Up to three characters, uppercase letters and digits. It fills in from the name, and MKT gives you MKT-123.
  • Description, optional.
  • Network, which is either Public to the workspace or Secret. See below.

Creating a project needs Member access to the workspace. A workspace can be set so that only admins create projects, in which case a member is told admin access is required.

The identifier can be changed later, and has to stay unique in the workspace.

What a new project starts with

You do not have to set a project up before using it:

  • Six states: Backlog (the default), Todo, In Progress, Done, Cancelled and Triage.
  • A set of labels, and a Fibonacci estimate scale, already active.
  • Auto-archive after about a month, so finished and cancelled work leaves the board on its own. Change it in the project's settings.
  • A chat channel for the project.
  • You as its admin.

How many you get

PlanActive projects
FreeOne
Starter, Pro, EnterpriseNo limit

"Active" means not archived and not deleted, so archiving a project you are finished with frees the slot.

A Free workspace that is over its limits, on projects or on members, goes read-only for new work: changes come back refused until you are under the limit or on a paid plan. Reading everything you already have keeps working, and so do billing, exporting and leaving the workspace. Nothing is deleted when you downgrade.

Who can see a project

This is the part worth reading carefully, because the answer is not the same for every role.

NetworkWho sees it in the project listWho can open it
PublicEveryone in the workspaceEveryone in the workspace
SecretIts members, and workspace adminsIts members only

A secret project is invisible to ordinary workspace members. They do not see it in the list, and a task key from it reports as not found, exactly as a key that never existed would.

A workspace admin is the exception, and it is worth being precise about it. An admin who is not a member of a secret project still sees the project in the list: its name, its identifier and its counts. They cannot open it, and they cannot read its tasks. They can still delete it, and they can change its settings, because administering the workspace includes administering its projects. If your reason for a secret project is to keep something from everyone including the people who run the workspace, a secret project is not the tool for that.

Guests see only the projects they have been added to.

Switching between them

A project can be switched either way in its settings, under Network.

  • Making a project secret needs Pro, whether at creation or afterwards.
  • Making a secret project public needs no plan.
  • A secret project in a workspace that drops to a lower plan stays secret. Nothing is exposed by a downgrade.

Only a project admin adds members, and each person is added at a role for that project, independently of their workspace role.

Per-project features

Settings, then Features, switches whole tabs on and off for one project. A project tracking a support queue does not need sprints, and a project of two people does not need modules.

ToggleDefaultWhat it hides
SprintsOffThe Sprints tab
ModulesOffThe Modules tab
PagesOnThe Pages tab
Inbox / IntakeOffThe intake inbox
Time trackingOffTimers and logged time

Views cannot be switched off.

Three things to know:

  • Sprints and modules start off. A new project is a flat list of tasks until you decide otherwise, which is why a brand new project has no Sprints tab.
  • Switching a tab off hides it, and keeps the data. It removes the tab from the project's navigation. Nothing is deleted, and switching it back on brings everything with it.
  • The Roadmap tab disappears only when both Sprints and Modules are off, since those are what it draws.

Changing these needs admin on the project or on the workspace.

A toggle is not a plan gate. You can switch Sprints on in a Free workspace; opening the tab then offers you the upgrade, because creating a sprint is what needs Pro.

Archiving and deleting

Archiving takes a project out of the active set and frees a plan slot. It needs admin on that project, so a workspace admin who is not a member of it cannot archive it.

Deleting is a soft delete. It needs admin on the project or on the workspace.

Troubleshooting

What you seeWhat it means
"The Free plan allows 1 active project(s). Upgrade in settings > billing to create more."Archive the project you are no longer using, or move to a paid plan.
"This workspace is over the Free plan limits"Too many members or projects for Free. Writing is blocked until you are back under the limit, or on a paid plan. Reading is not affected.
"Project creation requires admin access in this workspace."The workspace is set so only admins create projects.
"Identifier must be uppercase letters and digits only, max 3 chars"MKT works, Mkt-1 does not.
"Project identifier already exists in this workspace"Another project has that prefix. Task keys have to stay unambiguous.
"Secret projects require the Pro plan or higher."Making a project secret needs Pro. Creating it public does not.
"Project not found" when you can see it in the listYou are a workspace admin who is not a member of a secret project. The row is visible, the contents are not.
"Workspace member access required"Guests cannot create projects.
A new project has no Sprints or Modules tabThey are off by default. Turn them on in Settings, then Features.