Custom Card Templates
In addition to the three built-in card types (Requirement, Basic, Simple), project creators can define custom card templates. This lets you tailor the card structure to match your project’s specific workflow.
When to use custom templates
Section titled “When to use custom templates”Use a custom template when the built-in types don’t fit your needs. Common examples:
- API Contract — a card type for documenting API endpoints with specific fields
- Data Migration Requirement — includes fields for source system, target system, and data owner
- Non-Functional Requirement — security, performance, or compliance items with a distinct approval track
- Design Decision — a card for capturing architectural or design choices that need Client sign-off
Creating a custom card template
Section titled “Creating a custom card template”- Go to Project → Settings → Cards
- Click Create New Card Type
- Configure the template:
Name and appearance
Section titled “Name and appearance”| Setting | Description |
|---|---|
| Name | The card type name shown on the card and in the block menu |
| Short code | A 2-4 character prefix used for the card ID (e.g. “API”, “NFR”) |
| Colour | The accent colour for this card type |
| Border style | Left thick (for formal requirements) or full thin (for notes and lightweight items) |
Components
Section titled “Components”Drag the components you need from the Available pool into the card zones:
- Top-left — typically Type and/or ID
- Top-right — typically Members, Approval State
- Footer-left — typically Approval Process
- Footer-right — typically Approval
Not every card type needs the full approval workflow. A “Design Decision” card, for example, might only include Type and Members — skipping the formal Approval component if informal agreement is sufficient.
Content type
Section titled “Content type”Choose whether the card body should support:
- Heading + blocks — a title line followed by rich text (default for Requirement cards)
- Blocks only — freeform rich text without a forced heading (default for Basic cards)
Editing an existing template
Section titled “Editing an existing template”Go to Project → Settings → Cards, find the template, and click Edit. Changes to a template apply to all new cards created with that type. Existing cards retain their current structure.
Predefined vs custom templates
Section titled “Predefined vs custom templates”The three built-in types (Requirement, Basic, Simple) cannot be deleted — they are predefined and always available. Custom templates can be edited or deleted at any time from Project → Settings → Cards.