How Saga Feedback Boards and Roadmap Statuses Are Organized

Updated

Saga Feedback (sagahq.canny.io) is a public Canny-powered board where users submit and vote on product ideas for Saga. Content is split into two areas: a Feature Requests board where ideas are posted and voted on, and a Roadmap view that groups those requests by development status — Planned, In Progress, and Complete. If you want to influence what Saga builds next, search the existing requests first, add your vote, and only post a new request if nothing matches.

The two main areas

Area What it holds How to use it
Feature Requests The full list of submitted ideas (95 requests at the time of the page snapshot) Browse, search, filter, vote, or submit a new request
Roadmap The same requests grouped by status Check what is planned, being built, or already shipped

The page header offers Search, Boards, and Filters, plus a Log in link. Logging in is what lets you vote and post; the page does not state whether browsing is restricted without an account, so treat login as the safe assumption for any action beyond reading.

How statuses work

Each request carries one of three statuses, and the Roadmap view is essentially a status filter over the Feature Requests board:

  • Planned — accepted for future work. Examples from the board: "Ability to multi-select pages as tags in a collection from other collections" and "Mention collection as context in Saga AI."
  • In Progress — actively being built. Example: "Saga AI search across your workspace."
  • Complete — shipped. Example: "iOS mobile app."

Requests without a status label are open ideas still collecting votes. The status is the single most useful signal for deciding whether your feedback is already being acted on.

Reading a request

Every entry shows a vote count and a title, and many include a short description. The vote count tells you how much demand already exists — for instance, "Offline mode" shows 48 votes, "iOS mobile app" 38, and "Kanban View" 31, while newer items like "Add tasks to a collection" sit at 3. High-vote items are the ones most worth checking before you post, because a duplicate splits support rather than adding to it.

A practical workflow before posting

  1. Search first. Use the search box with the feature name you have in mind (e.g., "offline" or "table").
  2. Filter by status if you only care about what is coming: switch to the Roadmap view or apply a Planned / In Progress filter.
  3. Vote on a match. If an existing request covers your need, add your vote and, where the board allows, a comment explaining your use case.
  4. Post only if nothing matches. Submit a new request with a clear, specific title — the board's strongest entries are concrete ("Sortable tables," "Resize / change column width in tables") rather than broad.

For example, if you want better table handling, you would find several related requests already — "Formatting for tables," "Sortable tables," "Resize / change column width in tables," and "Add ability to insert row or column mid-table" — and should vote on the closest one instead of creating a fifth.

What the board tells you about Saga's direction

The distribution of requests is itself informative: a large cluster concerns tables and formatting, another concerns AI features (Saga AI context and workspace search), and a third concerns mobile and offline access. The "Complete" items — the iOS app and code-block wrapping — show the team does close out requests, so a vote is not a dead end. Use the Roadmap view as your first stop when you want to know whether a feature you need is already on the way.