Creating a Project

Projects live inside organizations and are the container for all your issues. Each project gets a unique slug that is used in issue reference codes.

Creating a Project

1. Navigate to the organization where you want the project.
2. Click New Project.
3. Fill in the project details:
   • Name — the display name for the project.
   • Description — an optional summary of the project's purpose.
4. Click Create Project.

Project Slug

Each project is given a slug — a short, URL-safe identifier derived from the project name. The slug is used as the prefix in issue reference codes (e.g. a project named "Backend API" might get the slug backend-api and issue codes like BACKENDAPI-1).

Slugs are unique within an organization. You can customise the slug during project creation but it cannot be changed after issues have been created.

GitHub Integration

Projects can optionally be linked to a GitHub repository. This enables GitHub commit panels to be shown on issues. To connect a repository:

1. Open the project and go to Project Settings.
2. Enter the GitHub repository in owner/repo format (e.g. acme/backend-api).
3. Enter the default branch (e.g. main).
4. Provide a GitHub personal access token with repo scope. The token is encrypted at rest.

Project Access Control

By default, all team members with access to the organization can view the project. You can restrict access to specific members from Project Edit → Assigned Members. Members not on the project list will not see it in the project index.

Tags

Projects support a custom tag system. Tags are created at the project level and can be applied to any issue within that project. Manage tags from the project's Tags page (accessible via the Tags button on the issue list).

Editing & Archiving a Project

Project settings (name, description, GitHub integration) can be updated at any time from Project Settings → Edit. When Archiving a project you have the option to move all issues to another project or archive all of its issues.