# Feature request tracking that shows real demand

> Open-source feature request tracking software. Gather requests from your portal, widget and support inbox, rank them by votes and tell everyone when it ships.

Source: https://quackback.io/use-cases/feature-requests

Customers post and vote on a board you own. Requests from chat and email join the same list. When you ship, everyone who asked hears about it.

## Collecting requests is easy. Keeping track is the job.

Requests arrive in support chats, sales calls, emails and your app. Feature request management means keeping one list, counting the same ask once, knowing who is behind every vote, and telling them what happened. Quackback does that bookkeeping so your team can make the call.

- **Product managers**: Rank requests by votes and by who's asking, then plan from the same list.
- **Support teams**: Add a customer's ask to the right request from the inbox, without copying it anywhere.
- **Founders**: Start on the Free plan with one board, and keep the list as the team grows.

## From request to release

Every request follows the same path, and the people who asked can see each step.

### 1. Customers post and vote

Your portal and in-app widget let customers post requests and vote on others. Similar posts appear as they type, so votes add up on one request instead of ten.

[Explore feedback boards](https://quackback.io/features/feedback)

### 2. Support adds what it hears

When a customer asks for something in chat, add it to the request from the inbox. Quackback counts their vote and keeps their words on the post as an internal note.

[Explore the inbox](https://quackback.io/features/inbox)

### 3. Plan it in the open

Move a request to Planned and it shows on your public roadmap. With Linear, Jira or GitHub connected, the linked issue reports its progress back, and Linear and GitHub update the status on their own.

[Explore the roadmap](https://quackback.io/features/roadmap)

### 4. Tell everyone who asked

Link a changelog entry to the requests it ships, and everyone who voted gets the news. Customers learn that asking works.

[Explore the changelog](https://quackback.io/features/changelog)

## What feature request management needs

- **Votes with names**: One vote per customer, totals on every request and the list of who voted. Add a vote for a customer who asked on a call.
- **Duplicates, merged**: Merge requests that ask for the same thing and every vote and comment carries across. Quackback AI suggests the merges for you.
- **Statuses people follow**: Use your own statuses. Voters and commenters are subscribed automatically and hear when one changes.
- **Demand by segment**: Filter requests by the segment of the customer who posted them, such as plan or company, to see what each group asks for. On Business.
- **Synced with your tracker**: New requests can open issues in Linear, Jira, GitHub and other trackers. Linear and GitHub update the request's status on their own; Jira, GitLab and most others suggest the change for you to approve. On Business.
- **Bring your backlog**: Import posts from a CSV exported from any tool, so your history comes with you.

## Frequently asked questions

### What is feature request tracking?

Feature request tracking is keeping every request customers make in one list, with how many people asked, who they are and what you decided. A tracker like Quackback adds voting so demand is counted, statuses so customers can follow along, and notifications so they hear when it ships.

### What is the best feature request tracking tool?

The best one depends on where your requests come from and who needs to follow them. Look for voting, statuses customers can see, emails when you ship and a link to your issue tracker. Quackback has all four, with issue tracker integrations on Business and up. It takes requests from your portal, in-app widget and support inbox, and it's open source, so you can use our cloud or self-host it.

### How do you prioritize feature requests?

Start with demand: votes show how many customers want something, and the voter list shows who they are. Then weigh it against effort and strategy, for example with a RICE score. Quackback sorts requests by votes or recency, and on Business you can filter by segment to see what your largest accounts have asked for.

### Can customers see the status of their requests?

Yes. Each request shows its status on your portal and widget, and planned work appears on your public roadmap. Voters and commenters are subscribed automatically, so they hear when the status changes and when it ships.

### Can I move our existing requests into Quackback?

Yes. Export your requests from your current tool or spreadsheet as a CSV and import them as posts. From then on, customers vote on them and your team triages them like any other request.

### Is there a free feature request tracker?

Quackback's Free plan includes one board with up to 50 posts, voting, a public roadmap, a changelog and Basic AI usage, with Copilot. Pro adds unlimited boards and posts and the AI agent, and Business adds issue tracker integrations and segments. You can also self-host the open-source edition with every feature.

## Related

- [Product management](https://quackback.io/use-cases/product-management): Turn request data into a roadmap you can defend.
- [In-app feedback](https://quackback.io/use-cases/in-app-feedback): Collect requests inside your web and mobile apps.
- [Feature voting](https://quackback.io/features/voting): How votes, sorting and trending work.

Start a free trial: https://app.quackback.io/signup?plan=pro&from=markdown
