1. Create a project

A project holds your repositories, pipelines, tasks and people. Start with one; you can add more later.

Create it

Projects → New project.

• Name — what humans call it, e.g. Demo Service.
• Key — the short prefix used in task IDs. DEV gives you DEV-1, DEV-2. Pick it deliberately: it shows up in every task reference, branch name and CLI command.
• Lead — optional, defaults to you.

Choose how the project tracks work

The Task tracker section decides which statuses and task types the project starts with. The default Preset → Software Dev is what this walkthrough uses:

• statuses Backlog → To Do → In Progress → In Review → Testing → Done, plus Cancelled;
• task types Story, Bug, Task and Epic, each with its own fields.

The form previews both lists before you commit, and you can refine them later.

The other tabs exist for teams that already have a process: Organization reuses a workflow shared across projects, External tracker syncs with a system like Jira, Custom starts from scratch.

Press Create project.

Note

Create the project in the UI rather than through the API when you are starting out. The preset — workflow, statuses, task types — is applied by the form; a project created bare through the API has no task types, and you will not be able to create a task in it.

What you get

The project page shows counters — repositories, connected, needs attention, open tasks, members — and, while it is empty, a direct Connect repository call to action. That is the next step.

Next

Connect a repository.