Skip to content

Board Management

Boards provide visual workflow tracking powered entirely by YAML definitions.

Configuration

Boards live in .kiket/boards/*.yaml. Each file can define one or many boards. Required keys:

name: Development Board
workflow: development
columns:
  - key: backlog
    name: Backlog
    wip_limit: 999
  - key: in_progress
    name: In Progress
    wip_limit: 4
    policies:
      auto_assign: true
  - key: review
    name: Review
  - key: done
    name: Done

Optional sections: - swimlanes to group issues by label, priority, or custom field. - filters for saved queries. - cards for custom field display and color rules. - automations to trigger actions when issues enter/leave columns.

Rendering Flow

  1. Repositories sync via SyncWorkflowRepositoryJob.
  2. BoardLoader parses YAML and builds normalized board objects.
  3. BoardConfigurationService creates/updates Board records, storing YAML provenance and runtime preferences.
  4. The frontend (Hotwire controller) reads metadata through data-workflow-states attributes and renders columns.

Managing Boards

  • Edit the YAML file, commit, and push. Kiket updates the board after sync. There is no UI editor to avoid drift.
  • Pin boards as favourites per user; these preferences live in the database and survive YAML updates.
  • Use board filters to focus on sprints, releases, or teams.

Validation

  • CI can run kiket workflows lint to validate definitions before deployment.
  • Runtime validation reports errors in the project activity feed with pointers to the file and line number.

Boards stay consistent with your workflows because the same YAML describes both the states and the visualization.