Projects
Group issues under a project with its own key and issue numbering, a status, a color, and a lead — the container every issue belongs to.
On this page
What a project is
A project groups related issues and gives them a key, like WEB-12. Each project owns its own issue numbering, so keys stay stable and readable. Every issue belongs to exactly one project — which is why you need at least one project before you can capture work.
Project fields
- Name
- The human-readable project name.
- Key
- 2–6 letters or numbers starting with a letter (for example
WEB). It prefixes every issue key and can't be changed after the project is created. - Description
- What the project is for.
- Status
- Planned, Active, Paused, Completed, or Canceled. New projects start Active.
- Color
- A swatch used to identify the project in lists and the graph.
- Lead
- An optional owner — any member of the workspace.
Creating and editing
Click New project on the projects list, give it a name and a key, and optionally set a description, color, and lead. To change details later, open the project and choose Edit — everything is editable except the key.
Note
Creating and editing projects needs the member role or higher; archiving needs admin.
The project page
A project's page lists its issues grouped by status, with a count per group, so you can see the shape of the work in one place. Create a new issue straight into the project from here.
Archiving
Archive a project to hide it from active lists and stop new issues from being created in it. Existing issues are untouched, and you can restore the project at any time. Projects are archived, never deleted, so history is preserved.
Improve this article
Spot something missing, outdated, or a broken link? Send the docs team a note.