Manage feature requests

Improve request titles and descriptions with AI

When creating a feature request in featurevote, write a description of at least 20 characters. Two options appear:

• Enhance Description rewrites the description to be clearer and more professional.
• Generate Title suggests a title based on the description.

The suggestion appears next to your text. Choose Accept to use it or Dismiss to keep what you wrote. Start with a specific description: vague input produces vague output. These tools can help when an idea is clear but hard to phrase, when you need a matching title, or when you want more consistent wording across requests.

Draft a release note without rewriting the customer's request

Marking a request Completed (the stable status value is done) opens the completion dialog. It shows the customer's original request and a separate release note with its own Title and Description. Leave the release note empty to use the request instead.

Open Generate Release Note, then choose Generate to draft a note from the request. Review it, edit it if needed, and accept the draft. The original request is never rewritten. The post retains the customer's words and shows the release note below them in a Shipped block. Voters receive the note in the completion email, and the next changelog uses it.

The AI changes request wording into announcement wording—for example, “We need dark mode” becomes “You can now enable dark mode.” Check that the claimed functionality actually shipped: AI can turn a hesitant “maybe” into a confident “you can now.”

Source: Improve request titles and descriptions with AI

Set request statuses

Update a request from the feature list or its detail view. The dashboard statuses are Requested (new, not yet decided), Planned (approved, not started), In Progress (being built), Completed (shipped), and Not Planned (won’t be built). Requests marked Not Planned drop out of Feedback Portal lists and search. Marking a request Completed opens a completion sheet; Notify Voters is on by default, and voters who left an email receive the news. When Known issues is enabled, bugs use these same dashboard statuses but display different stage names on the Feedback Portal; see the Known issues guide.

The shipped feature status has the stable value done. Some guides call it Done; the current status label is Completed. With Known issues enabled, shipped bugs use Fixed.

Open a request, then scroll to its comment section to reply as the team. Your comment appears publicly marked Team. Users can reply in the same thread, and the request card shows Team replied after your team has commented. Comments can include images.

Use the Working on it field to assign a team member. Requests you create, and requests you convert from the Feedback Inbox, start assigned to you. You can change the assignment and filter the list by Everyone, Mine, Unassigned, or a named member. Assignments are internal and are not shown on the Feedback Portal.

Open the request detail view or select its vote count, then use Add a voter by email. Search for a contact by name or email and select them, or enter a new email; you can add a name for a new voter. Select Add vote to record the vote against that email. Existing contacts keep their saved name and email-subscription preference. A new voter is subscribed. If the person already voted, the button reads Remove vote instead.

When creating or editing a request, choose Add images, or paste or drop images into it. A request can hold up to three images. Admins can see them in the request detail view; images on public requests are also visible to board visitors.

In a request’s create or edit dialog, select Private Feature to make that individual request visible to your team in the admin dashboard but hidden from the public Feedback Portal, its search, and the public roadmap. Private requests do not collect public votes or comments. If a request already has votes, they stay attached while it is private; making it public again restores them. You can toggle the setting at any time. This is separate from board visibility settings, which control access to the whole board.

Every request is an idea or a bug. To change its type, open its edit dialog and choose Idea or Bug under Type. Bugs and ideas appear in the same dashboard list and roadmap. When Known issues is enabled, visitors can choose a type when posting, and open bugs have their own Feedback Portal tab.

On the Feedback Portal and in embeds, featurevote automatically checks a new request for close matches before creating it. If it finds any, the submitter sees up to three existing requests and can vote for one, submit anyway, or edit their draft. This check is advisory and does not block submission; if it cannot run, the request submits normally. For bugs on a board with Known issues enabled, matching compares bugs with bugs and ideas with ideas. This automatic pre-submission check is separate from the admin tool for finding and merging requests that are already on the board.

Users often submit the same request in different words. AI can detect these automatically. Select a feature request from your list, choose Find Duplicates, review the similarity scores and suggested matches, then select the requests to merge and choose Next Step followed by Confirm Merge. Votes and comments from merged requests consolidate onto the primary request.

With Known issues enabled, the Feedback Portal uses Reported, Confirmed, Fixing, and Fixed for bugs; the dashboard uses its usual status names. A bug marked Not Planned leaves the Known issues board. When you mark a bug Completed, voters who left an email can be notified if Notify Voters is ticked; the bug email says Fixed and its subject uses Fixed - "…".