Where labels work hardest

Issue trackers: Jira, Linear, Asana

Trackers are where labels do their most formal work. A code-style label (PRJ-042 Website Redesign) becomes the project's identity across epics, tickets and reports.

What works: prefix + number + plain name, enforced at project creation. The number guarantees uniqueness; the plain name keeps humans oriented. Link the code in every related doc so search finds the cluster.

Watch out: do not let teams invent their own prefixes per project — one shared prefix list (in your conventions doc) prevents PRJ, Proj and PROJECT from coexisting.

Docs and wikis: Notion, Confluence, Google Docs

Docs sprawl. Tags (#WebsiteRedesign) and consistent page-title prefixes ([PRJ-042]) make the sprawl searchable. When every page about a project carries the same tag, one search reconstructs the whole story.

What works: put the code or tag in the page title itself, not just the body — titles are what search indexes first and what people see in link previews.

Code: repos, branches, folders

Repositories, branches and folders need slugs: lowercase, hyphenated, no spaces. website-redesign-042 works in git, URLs, scripts and every OS without quoting or escaping.

What works: repo name = slug, default branch prefixes = ticket codes (prj-042/header-tweak). Anyone can trace a branch to its project in seconds.

Chat: Slack, Teams, Discord

Chat moves fast and labels are how you keep up. A channel per project named with the slug (#proj-website-redesign) plus a tag for cross-channel mentions covers both organized discussion and drive-by references.

What works: pin a message with the full label kit (code, slug, tag, docs link) in each project channel. New joiners orient themselves without asking.

Client work and agencies

Client projects need two faces: a professional external label (ACME Website Redesign) and whatever internal shorthand the team prefers. Never let an internal codename leak into a client deliverable — it reads as unserious at best and confusing at worst.

What works: client prefix + descriptor + year (ACME-Website-2026) for files the client sees; codenames stay in internal channels only.

Personal and side projects

For solo work, labels fight a different enemy: your own future forgetfulness. A descriptive slug with a year (recipe-app-2026) beats "new-project" every time you browse old folders.

What works: one folder-naming habit applied to everything, plus a codename if the project needs motivation. Future-you is a stranger — label for them.