Projects

Create a project, choose its key and template, manage its team, make it private, turn on triage and archive it.

Sidebar → Projects

A project holds a body of work: its issues, board, backlog, sprints, releases and team. Most teams have one project per product, service or stream of work.

Create a project

Choose the + next to Projects in the sidebar.
Enter a Name (2 to 80 characters).
Check the Key. It is suggested from the name, for example "Platform Core" becomes PLC, but you can type your own. A key is 2 to 10 capital letters or digits, starting with a letter, and must be unique in the workspace.
Under Start from, keep Blank project or pick a project template.
Pick a Kind: Software, Support, Internal or Customer success.
Choose Public or Private under Visibility, a Color, and optionally a Description.
Choose Create project.

You become the project's lead and its first team member. The project starts with a default board whose columns come from its workflow. Creating projects is for Owners and Admins, or a custom role that allows it.

The key cannot be changed after the project is created. It is the prefix of every issue key, such as PLT-123, so choose a short one that says what the project is.

Templates

A project template brings its own trackers, workflow, labels, Definition of Done and board, so a new project starts set up the way your team works. To make one from a project you already have, open its Settings and use Save as template. See Project templates.

Who can see a project

Public: every member of the workspace can open it. Guests still see only the projects they were added to.
Private: only the project's team, plus the workspace's Owners and Admins, who see every project.

Privacy covers everything in the project, not just its name: its issues, comments, sprints, boards and reports are hidden from everyone outside it, and people outside it are not offered in its mention and people pickers.

The project team

The Team tab of a project lists the members with explicit access to it. The project lead, Owners and Admins can manage it.

Pick someone in Select member to invite… (only existing workspace members are listed).
Optionally give them a team role, such as QA or Developer.
Choose Add.

Team roles are labels that describe what someone does on the project. They do not change their permissions. Owners and Admins define the list in Settings → Team roles. Assignee pickers on a project offer its team.

You cannot remove the project lead from the team. Give the project a new lead in its Settings first.

Project settings

The project's Settings tab is for the project lead, Owners and Admins. Everyone else sees it read-only, if at all. It has these sections:

General: Project name, Description, Color, Project type and Project lead. The key is shown but cannot be changed.
Workflow: the Default workflow, Default assignee and Default priority.
Access: switch between Public and Private.
Triage: see below.
Source control and Figma: link repositories and a Figma account.
Definition of Done, Save as template and the Danger zone.

Choose Save changes at the bottom after editing.

Triage on or off

Turn on Triage new issues from outside the team to stop issues from forms, email, chat, monitoring alerts, the API, or anyone not on the project's team from landing straight on the board and backlog. They wait in the Triage inbox until someone on the team accepts, declines or snoozes them. See Triage.

Archive a project

Open the project's Settings and scroll to Danger zone.
Choose Archive, then Yes, archive.

Archiving does not delete anything. The project moves under Archived projects on the All projects page, leaves the sidebar and project pickers, and its issues are left out of workspace-wide issue lists. You can still open it from Archived projects.