Boards Overview
Boards give you a Kanban-style view of your requirement cards, organised into columns that reflect the status of your work. They bring together cards from one or more projects and give the whole team a shared view of what’s in progress, what’s waiting for approval, and what’s done.
What a board shows
Section titled “What a board shows”A board is a collection of columns. Each card in the system can be placed on one or more boards, in one of those columns. Moving a card between columns updates its position on the board — it does not affect the card’s underlying approval state.
Boards are a progress-tracking view, not a workflow enforcer. The formal workflow lives in the approval process; boards give you visibility across that process at a glance.
Typical column setup
Section titled “Typical column setup”A common board structure for a requirements management project might look like this:
| Column | What it contains |
|---|---|
| Backlog | Cards defined but not yet active |
| In Spec | Cards being written and structured |
| Awaiting Approval | Cards submitted to Clients for sign-off |
| Approved | Cards the Client has approved |
| In Development | Cards that have been synced to Jira and are being built |
| Done | Cards for completed work |
Columns are fully configurable — you can name them whatever makes sense for your team and project.
Multiple projects on one board
Section titled “Multiple projects on one board”A board can pull cards from multiple projects simultaneously. This is useful when a single delivery team is managing work across several related projects and wants one consolidated view.
Each board specifies which projects and card types it sources from. See Board Sources for configuration details.
Privacy
Section titled “Privacy”Boards can be set as private (visible only to the creator) or shared (visible to all project members). Use private boards for personal planning views; use shared boards for team-wide status tracking.