Getting startedSet up integrationsCreate your first initiativeInvite your teamPlan today's workShare your first update
Initiatives & BugsTaxonomyTriageOngoing Work
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


Triage

Triage reviews potential work before it becomes planned work.

Triage

What appears in triage

Triage contains potential work waiting for review: workspace items in In Review plus bugs and feature requests from connected apps. You may be listed as the reviewer, but triage is not an assignee queue for execution work.

Each triage item has a review workflow. The reviewer can comment, accept the item, decline it, mark it as a duplicate, or assign a different reviewer.

Triage a bug or feature request

Open the item and decide what should happen next. Accept it when it should move forward, decline it when it should not, mark it as a duplicate when it repeats existing work, or assign a reviewer when someone else should make the decision.

When you accept a feature request or bug that belongs with planned work, link it to the right initiative. For bugs, make sure the description has enough detail for the next person to investigate.

UI
Dashboard sidebar flickers on route transitions in dark mode

From the triage list, open any item to review the detail, comment, route the decision, or connect it to existing work.

Accepting a feature request or bug moves it forward as an initiative or bug. It appears in Backlog unless the reviewer chooses a different status or assignee during the decision. Declining closes it as cancelled. Marking it as duplicate closes it against the existing initiative or bug it repeats.

For the full decision model, including duplicates and retained visibility, see Triage Items.

A short walkthrough of reviewing incoming bugs, feature requests, and ideas before they become planned work.

For defect intake, pair triage with Bugs so reports have enough detail before planning.


PreviousTaxonomyNextOngoing Work

Initiatives & Bugs

Use initiatives for planned work and bugs for defects or incidents before work moves into planning or delivery.

Ongoing Work

Keep recurring streams visible without turning every cycle into a new project.

Taxonomy

Taxonomy connects initiatives, bugs, and activity to the goals, customers, products, and areas they affect.

Triage Items

Understand triage reviewers, decisions, duplicate handling, and backlog outcomes.

  • What appears in triage
  • Triage a bug or feature request
  • Back to top