Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
PlanningRoadmapBacklogPrioritiesBoardsOwnershipBlockers
DocsAPI Reference

Main

  • Home
  • About
  • Pricing
  • Vault
  • Changelog
  • Docs

Features

  • Roadmaps
  • Planning
  • Standups
  • Status updates
  • Insights
  • AI assistant / MCP
  • Integrations

Solutions

  • Startups
  • Dev shops / agencies
  • Software teams
  • Internal IT & platform teams

Alternatives

  • vs Jira
  • vs Linear
  • vs Asana
  • vs Monday.com
  • vs ClickUp
  • vs Notion

Company

  • Blog
  • Security
  • Log in
  • Sign up
  • Terms of Use
  • Privacy Policy

Resources

  • Docs
  • Community
  • API reference
  • CLI
  • Desktop app
  • SDK

© 2026 One Horizon. All rights reserved

FacebookInstagramThreadsXRedditTikTokYouTubeMedium


Boards

Use boards to coordinate planned work across statuses. Your personal Board shows the work tied to you across teams. Team board shows one team's work together.

Replacing an existing board app? Boards can become the primary planning surface. Keeping another app as the source of truth? Boards can show synced work next to native initiatives and bugs.

Boards

Personal board

Start with Daily recap when you need your personal view of today: completed work, planned work, blockers, and pull requests that need attention. Open the Board tab in the Daily recap header to see the same personal scope as a Kanban view across Planned, In progress, and Done. The Blockers column appears only when something is blocked.

The personal board lists work tied to you across the workspace: initiatives and todos where you are an assignee, issues assigned to you from connected apps, and pull requests that need your attention or that you authored.

Use the grouping control to switch between one combined grid, team rows, product rows, or skill rows. If something should appear on your personal board, your account needs to be an assignee in One Horizon or the connected app. Member grouping is reserved for team boards because the personal board is already scoped to you.

Team board

Expand a team in the sidebar and choose Team board. Each team has a kanban-style planning board. Statuses appear across the top, team members down the side, and each cell shows that person's work in that status.

You can group by member, team, product, skill, or use one combined grid. The board setting is saved per team and travels in the URL when shared.

Team board by status

Planned

Component library cleanup
Consolidate duplicate components, fix deprecated props, and update Storybook docs.

In progress

Design system icon library
Unified icon set with React components, tree-shaking, and accessibility compliance.

Done

PiperAPI v2 SDKs
Ship updated JS, Python, and Go SDKs with improved docs, examples, and error handling.

What boards include

Boards can show roadmap initiatives, bugs, ongoing work, synced issues, pull requests, and todos in one view.

Drag native work between columns to change status. Open a card for full details in the side panel or on a dedicated details page.

For synced issues, available status and assignment changes follow the source app and integration mapping. When grouped by member, drag between rows to reassign work where permissions allow.

Add new initiatives or bugs from column headers; the status is pre-set from the column.

The Blockers column appears only when blocked work exists. Open, Ideas, and Cancelled are additional columns and stay hidden unless enabled.

Boards complement recaps and the Journal. Recaps are day-focused, the Journal is a chronological archive of completed tasks, and boards are for scanning and moving planned work through status columns.

Use Recaps for day-focused summaries and Ownership when board movement exposes unclear owners, assignees, or reviewers.

Frequently asked questions


PreviousPrioritiesNextOwnership

Related Articles

Backlog

Hold ideas, bugs, and feature requests until they are clarified, prioritized, or declined.

Blockers

Make stuck work visible with the dependency, decision, or missing input attached.

Ownership

Show who is responsible for moving work forward and who needs visibility into it.

Priorities

Explain what happens next and why one item deserves attention before another.

  • Personal board
  • Team board
  • What boards include
  • Frequently asked questions
  • Back to top