If your team plans its work in Linear, there are two ways to collect feature requests there. Linear's own Customer Requests let the people who talk to customers attach each request to an issue, with the customer and their revenue beside it. That works while requests reach your team through support and sales. Once customers should ask and vote themselves, they need a board of their own, linked to Linear issues so that nobody copies anything between the two.
What Linear's Customer Requests do#
Customer Requests is a Linear feature an admin turns on in the workspace's settings. Here is what Linear's documentation describes, as of October 2026:
- A customer is a company, with a domain, a logo and attributes: revenue, size, tier and status. Requests find their company by the email domain of the person who asked.
- A request is a link between a customer and an issue or a project, usually quoting what they said. Members add one by hand, or it arrives from Intercom, Zendesk, Front, Slack or Linear's Asks, depending on the plan.
- Views rank the work by demand: filter issues by customer, tier or revenue, and sort them by the number of customers who asked. A triangle marks the requests that are important to a customer.
- Members are notified when a request lands on an issue they follow, and a customer's page can tell its followers when one of that customer's requests is completed.
For a team that sells to a few dozen companies, through account managers who write everything down, this is a good fit: the request sits next to the work, and nobody opens another tool.
Where it stops#
Every request in Linear goes through someone on your team. That's deliberate, and it has three consequences:
- Customers can't ask by themselves. A request exists once a member, or a support conversation, puts it there. What a user mentions in passing, and nobody forwards, never arrives.
- Customers can't vote. The count is of the customers someone added. Twenty people who would each click a button leave no trace unless twenty requests are written by hand.
- Customers don't see it. Linear's page describes no portal and no public list. The notifications go to your members, so telling the customers who asked that it shipped is still someone's job.
None of this is a flaw in Linear. It's a tool for the people who build, and it keeps customers out on purpose. The question is whether your customers should have a place of their own.
When you need a board as well#
Customer Requests alone are enough when you have few customers, each with someone on your team who speaks for them. Add a board when one of these is true:
- Many users, few conversations. A product with thousands of self-serve users hears from a fraction of them. A board in the app turns the rest into votes.
- You want to know who else wants it. On a board, the next person with the same need finds the request and votes, instead of writing a new ticket.
- People should hear back. The people who voted for or followed a request are told when its status changes, and when it ships.
- You want requests ranked by what they're worth. Votes count people. Weighted by the companies behind them, they count revenue, as Linear's views do.
The board is for intake: customers write in their own words, and the team merges duplicates and decides. Linear stays the place for the work. What matters is the link between the two.
A board for customers, the issues in Linear#
Nothing should have to be copied between the board and Linear. With Swingback's sync Beta, a request on the board links to issues in Linear (and on GitHub), up to 20 of them, and each side follows the other.
- Create the issue from the request. A member picks a Linear team and writes the title and text for engineers. Swingback adds no customer's name, email or company to the issue: its text is what the member confirms before it's created, or, for an automatic issue (below), the request's own title and text.
- Engineers see the demand on the issue. Each request is two attachments: its page in your dashboard, with its votes, and its page on your portal.
- Linear's states move the request. By default a state's type decides: Unstarted makes the request Planned, Started makes it In progress, Completed completes it, and Canceled closes it. Triage, Backlog and Duplicate change nothing. You can choose otherwise per workflow state.
- The request moves its issues too. Set a request to Planned, and its issue goes to the first workflow state that gives Planned, or the one you chose.
- Comments cross with no names added. What customers write reaches the issue as a quote under "A customer commented
on" and the request's title. What engineers write in Linear comes back as an internal note, which the portal never
shows. To let them answer customers, turn on Let a comment's author publish it with
/swingback-public: a comment with that line then shows on the portal. - Routing rules pick the team Beta. Posts of the "Mobile" board go to the mobile team, posts tagged "billing" to another. With automatic issues on, a request that becomes Planned gets its issue without anyone opening the dialog.
The application acts as itself in Linear, so it takes no paid seat. It adds attachments, never Customer Requests, so your account managers' requests stay theirs. Use both: Customer Requests for what sales hears, the board for what users ask themselves.
When the issue completes, the request completes, and the people who voted for it hear about it. That's the part I cared most about when I built it. A request that ships while the person who asked never finds out is a request you answered for nobody.
Setting it up#
- Under Settings → Integrations in Swingback, connect Linear. An admin of your Linear workspace installs the application and picks the teams it may reach.
- Enable the teams that take issues, and say what each one holds.
- Open a request, and create its issue from the Linked issues card.
GitHub and Linear in the docs has every step, what each state gives a request, and what leaves for Linear. If you're still deciding between issues and a board, GitHub issues for feature requests asks the same question for GitHub.
