Card Types

Every card has a type that determines its structure, visual appearance, and available metadata fields. Vanillaround includes three built-in types and supports custom types configured per project.

Built-in types

Requirement

The primary card type for formal requirements management.

Included components:

• Type label — the card’s category (e.g. Feature, Bug, Enhancement)
• ID — an auto-generated or manually set identifier
• Members — one or more team members assigned to this requirement
• Approval — the full approval workflow (Draft → Submitted → Approved/Rejected)
• Approval Process — defines which assigned members must approve
• Approval State — current state shown prominently on the card

Visual: Orange left border. Used for any requirement that needs formal Client sign-off before development.

Basic

A lightweight card for items that need tracking but not a full approval cycle.

Included components:

• Type label — the card’s category

Visual: Yellow full border. Suitable for internal Provider notes, decisions, or items that are agreed informally rather than through the formal workflow.

Simple

The most minimal card — a title with a type label.

Included components:

• Type label

Visual: Grey left border. Useful for placeholders, ideas under consideration, or items still being defined.

Custom card types

Project creators can define additional card types in Project → Settings → Cards. A custom card type lets you choose:

• Name — what the card type is called
• Colour — the card’s visual accent colour
• Short code — a brief identifier prefix (e.g. “REQ”, “BUG”)
• Components — which metadata fields to include (from: Type, ID, Priority, Due Date, Members, Approval, Jira, Boards)
• Border style — left thick or full thin

This means you can create project-specific types like “API Contract”, “Data Migration”, or “Non-Functional Requirement” — each with exactly the metadata your team needs.

See Custom Card Templates for step-by-step instructions.