Project Settings

The General, Board, Integrations, Agents and Team tabs of a project

Open Project Settings in the sidebar. The surface has five tabs, each a page of its own: General, Board, Integrations, Agents and Team. A personal project shows General, Board and Team only, because it has no integrations and no agent seats.

The project key is printed under the page heading. It is read-only: a key cannot be changed after the project exists.

General

Identity

  • Project Name, 1 to 255 characters.
  • Description.
  • Status: Planning, Active, On Hold, Completed or Archived. Status is the label the projects index files the project under. It does not lock the project.
  • Type: Software, Web, Mobile, Hardware or Hybrid.
  • Methodology: Scrum, Kanban, Hybrid or Personal. Changing it keeps every issue, epic, document and history entry. Moving to a methodology without sprints is refused while a sprint is running.

Cadence and estimation

  • Sprint Length: 1, 2, 3 or 4 weeks, or a custom number of weeks.
  • Release Frequency (weeks).
  • Working Days: which days of the week the team works.
  • Story Point Scale: Numeric (0-100), Fibonacci, T-shirt sizes or Hours.
  • Velocity Baseline in story points per sprint, used for capacity planning until the team has completed sprints.

These are hidden for a personal project, and the sprint fields are hidden for a methodology that has no sprints.

Quality and housekeeping

  • Definition of Ready: the checklist an issue should meet before it is picked up.
  • Auto-archive Done issues after (days): 1 to 365, or blank for off.

Dates and links

  • Start Date and End Date.
  • Repository URL, Documentation URL and Slack Channel.

Danger zone

One action: Delete. You type the project name to confirm, and the deletion cannot be undone. There is no separate archive action here; archiving is the Archived status above.

Board

The Board tab is where the project's columns are configured. There are seven statuses: Backlog, To Do, In Progress, In Review, Testing, Done and Deferred. Every status is either on exactly one column, or listed under Not shown on board at the bottom of the tab.

Each row gives you:

  • Column name.
  • Statuses: click a status chip to add it to this column or send it to Not shown on board. Picking a status that lives on another column moves it, which is how two statuses are merged into one column; a move that takes a status off a column asks first. The first status on a row is the primary one, and cards dropped there take it.
  • WIP limit: a switch and a number. Turning the switch off clears the number.
  • Colour: no colour, or one of eight presets.
  • Reorder: drag the grip handle, or focus it and use the arrow keys.
  • Delete: a column with no statuses is removed immediately. One that still shows statuses asks first, per status, where it should go -- a picker offering every other column plus Not shown on board, which is the default. This works even while a status still holds issues: they keep their status and simply stop appearing on the board.

Add column creates an unnamed row with no statuses. Save writes the whole layout at once; Reset discards your draft.

Not shown on board lists every status no column shows, each with the number of issues in it and a Move to… picker to put it on a column. Those issues stay off the board but still appear in List view and search.

Save stays disabled, with the reason shown, while any of these is true:

  • A status appears on two columns.
  • Done has no column.
  • A column shows no status.
  • A column has no name.

Any other status can sit under Not shown on board, and Save works normally.

The Done column cannot be removed, and Done cannot be moved to Not shown on board, because velocity, cycle time and burndown all depend on knowing when work finished. Every other status can be removed from a column here even while it still holds cards -- they keep their status and land wherever the removal dialog's picker sent them, Not shown on board by default. The board's own kebab Remove column, on the board itself rather than in settings, is stricter: it is offered only while a column's statuses are empty.

Editing the layout is open to members whose role is not view-only. Removing a column is restricted to the project owner and project leads.

Integrations

Connect this project to a code host. A project can hold several repositories, one connect call each.

  • GitHub: connect or disconnect a repository, and choose the default branch.
  • GitLab: the same shape.

Webhooks and the Slack and Teams integration have their own pages. See GitHub Integration, Slack and Teams and Webhooks.

Agents

Which agents are linked to this project. Built-in role agents are linked when a business project is created; add or remove them here.

Team

The people and agents on the project, their roles, and pending invitations, which you can cancel or resend. See Team Management.

Where other settings live

Some things a reader often looks for here are set elsewhere:

  • Notification preferences are per person, not per project. See Notification Types.
  • Automation rules live on their own Automation page.
  • The seven built-in issue types are fixed, and are not enabled or disabled per project. A project can define custom types of its own. See Issue Types.
  • Issue templates live on their own page. See Issue Templates.

Next: Workspaces.