> ## Documentation Index
> Fetch the complete documentation index at: https://docs.claboard.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# Task Keys

> Jira-style identifiers for every task

Every task in Claude Board gets an auto-generated key in the format `{TYPE}-{PROJECT}-{NUMBER}`, similar to Jira issue keys.

<Frame>
  <img src="https://mintcdn.com/bahri/LhHfZeA1RQn4U7C6/images/feature-task-keys.svg?fit=max&auto=format&n=LhHfZeA1RQn4U7C6&q=85&s=168157d60885dde1ab1b591a14fa4681" alt="Task Keys" width="900" height="280" data-path="images/feature-task-keys.svg" />
</Frame>

## Format

```
FTR-CB-1001
 │   │   │
 │   │   └── Sequential counter per project (starts at 1001)
 │   └────── Project key (derived from project slug)
 └────────── Task type prefix
```

## Type Prefixes

| Task Type | Prefix |
| --------- | ------ |
| Feature   | `FTR`  |
| Bug Fix   | `BUG`  |
| Refactor  | `RFT`  |
| Docs      | `DOC`  |
| Test      | `TST`  |
| Chore     | `CHR`  |

## Project Key

The project key is automatically derived from the project slug:

* Multi-word slugs use initials: `claude-board` → `CB`, `utd-games-website` → `UGW`
* Single-word slugs use first 3 characters: `renkler` → `RNK`

## Where Keys Appear

Task keys are displayed everywhere the task ID was previously shown:

* **Task cards** on the Kanban board
* **List view** rows
* **Timeline view** labels
* **Task detail modal** header
* **Live terminal** header

## Automatic Updates

* Keys are generated on task creation
* When a task's type changes (e.g., feature → bugfix), the prefix updates automatically (`FTR-CB-1001` → `BUG-CB-1001`)
* Existing tasks are backfilled with keys on server startup