Card Components
Cards are composed of modular components. Each component adds a specific piece of metadata or functionality to the card. Different card types include different combinations of components; custom card types let you choose exactly which components to include.
Available components
Section titled “Available components”A label that categorises the card within its type (e.g. “Feature”, “Bug”, “Enhancement”, “Non-Functional”). Providers set this when creating or editing the card.
Appears in the top-left corner of the card header.
An identifier for the card — useful for referencing requirements in conversations, emails, and Jira. Can be auto-generated or manually set (e.g. “REQ-042”).
Appears in the top-left corner alongside the Type label.
Priority
Section titled “Priority”Indicates the relative importance of the requirement. Options: Critical, High, Medium, Low. Useful for planning and sequencing work.
Due Date
Section titled “Due Date”A target date for the requirement to be approved or implemented. Provides a time-based signal for planning.
Members
Section titled “Members”One or more team members attached to the card. Members can be Providers (responsible for the requirement) or Clients (responsible for approving it).
Members appear in the top-right corner of the card. At least one Client member must be assigned before the approval workflow can be used.
Approval
Section titled “Approval”The approval control. Shows the current approval state and provides the Submit, Approve, and Reject actions. See Approval Workflow for full details.
Appears in the footer-right of the card (for Requirement card type).
Approval Process
Section titled “Approval Process”Defines whether any or all assigned Client members must approve for the card to reach the Approved state.
Appears in the footer-left of the card.
Approval State
Section titled “Approval State”A prominent visual indicator of the card’s current approval status (Draft, Submitted, Approved, Rejected). Shown in the card header for at-a-glance status.
Jira Issue
Section titled “Jira Issue”Links the card to a Jira issue. Once a Jira integration is connected to the project, this component lets you associate a card with an existing Jira issue or create one from the card.
The Jira issue key (e.g. “PROJ-123”) is displayed on the card and links directly to the issue.
Boards
Section titled “Boards”Shows which boards this card appears on. Cards can exist on multiple boards. This component lets you add or remove the card from boards directly from the spec page.
Component placement
Section titled “Component placement”Components appear in designated zones on the card:
| Zone | Position |
|---|---|
| Top-left | Type, ID |
| Top-right | Members, Approval State |
| Footer-left | Approval Process |
| Footer-right | Approval |
Custom card types let you arrange components across these zones when configuring the template.