Navigate to Tickets > Feature Requests to see everything your team has logged, and click New Request to add one - a title, a description, and an optional use case. A ticket of type "feature request" can also be turned into one directly, carrying its title and description along and linking back to the original ticket.
Anyone on your team can vote for a request they'd like to see built, or remove their vote later. Votes are one of the ways requests get ranked, and you can filter the list down to your own requests or the ones you've voted for.
When AI features are enabled, each new request is automatically scored on three dimensions: impact (how many users benefit, and how much), effort (how complex it looks to build), and alignment (how well it fits the kind of product you're building). Sort the list by AI ranking to surface high-impact, low-effort, well-aligned requests first. Requests are also grouped with similar ones automatically, so a request's detail page can show related requests already logged - useful for spotting duplicates before they pile up.
A request moves through submitted, acknowledged, planned, in progress, completed, or declined. Whoever manages your backlog can change its status, add manager notes, and set a manual priority order that overrides vote count or AI ranking when you want the final say. Changing status notifies whoever submitted the request.
Was this article helpful?