Areas
Organise work by system or domain (Auth, API, Frontend, Billing). Areas don't have a lifecycle; they exist as long as the system does.
An area is a piece of your system that you maintain over time. Unlike releases, areas don't have a lifecycle. They exist as long as the system they describe exists.
When to use areas
Use areas to model architectural surfaces or business domains: Auth, Billing, API, Frontend, Mobile, Marketing site. A common starting set:
- Auth: login, signup, password reset, OAuth.
- Billing: Stripe, invoices, subscription state.
- API: public endpoints and webhooks.
- UI: frontend components, pages, navigation.
Don't use areas for time-bounded initiatives; that's what releases are for. "Q2 launch push" is a release. "Frontend" is an area.
Creating areas
Areas can be created two ways:
- From the Areas tab: click New area, give it a name, an optional description, and a colour.
- Inline from any task or release dropdown: start typing a new area name and pick "Create area" from the suggestions.
Each area has a colour (used in card borders and labels), an optional icon, and an optional description.
The Areas page
The Areas page shows every area as a card with its total task count, a per-status breakdown with a progress bar, and the first line of its description.
Clicking a card opens the area edit modal, where you can rename or recolour the area. Each card also has a ⋯ menu with Edit and Delete.
Deleting an area
Deleting an area removes it for good. Its tasks show as "unassigned" until you tag them again.
Deleting an area never deletes tasks. Tasks are the work; areas are a planning shell, the same stance Releases take on deletion.
Plan limits
The free tier allows 5 areas per project. Indie and above remove the cap. See Plans and limits.