Backlog

Use the backlog for unscheduled initiatives, bugs, feature requests, and ideas captured from integrations or created in the workspace.

Replacing an issue tracker or product planning tool? Use the backlog as the intake queue for new work. If Aha! or Productboard owns discovery today, move accepted feature requests into ideas or initiatives. Using Linear, Jira, or another issue tracker? Keep synced issues in that app until the team decides to move them.

What you can do

Review incoming work before it reaches the roadmap or today's plan. Each row shows status, recent activity, when the item was created, and ownership. You can filter by kind, parent initiative, or owner, sort by columns, and open a detail panel by selecting an item.

Use the List and Board tabs in the header to switch between the table and a kanban of the same backlog items. Search, grouping, filters, and sorting apply in both views.

The default view groups items by work type. You can regroup by owner, assignee, team, product, customer, goal, or skill. Items with multiple assignees or teams appear under each matching group. The selected grouping is saved for the workspace and appears in the URL when shared.

Add work

Create an initiative or bug directly from the backlog. Both are created with Idea status so they stay in intake until someone decides to plan, assign, or decline them.

New initiatives can start in Writer Mode when the problem is clear but the brief is not written yet. When accepted work is ready to become a source brief for execution, use spec-driven development to decide what context belongs on the record.

Use the backlog for workspace-wide intake. Team boards are better once work is assigned and ready to move through statuses. For teams coming from an unconnected board app, start with current active work and leave old closed history behind unless it is still needed for reporting.

Use Priorities when backlog items need to be compared before they move into planned work.