Feature Requests

Sent a conversation to Autopilot where several valuable product insights were surfaced particularly around how integrations are positioned, emerging workflow use cases, and overall product messaging. Another model categorized these as "actionable product feedback," but Autopilot didn’t flag them because they didn’t meet its stricter definition of a feature request. The conversation included observations like: A key integration is supported but isn’t being adopted due to limited awareness Certain advanced workflows are technically feasible but not well-packaged or promoted Useful functionality exists but is difficult to discover or understand These weren’t framed as direct customer asks, but they clearly signal perception gaps and strategic opportunities. It would be useful if Autopilot could optionally extract this type of as a separate category from traditional feature requests.

I needed the webhook for changelog entries created / updated for invalidating my cache. I pull the changelog entries into my application and display them in a customer facing dashboard.

Display both votes by users and votes by users' companies.

mark posts that has unread comments across the feedback and roadmap.

It could be nice, if I could have the votes in click up aswell as a custom field?

Maybe using some tool that allows the community to work on the translations.

Limit the number of votes a user gets (say, 10-15 votes). As features are changed to Complete, give them those votes back to use on other features. I think this would really help surface the top features when people have to be more picky about the things they vote on.

It would be cool if users can reference existing posts with "@postname" in their posts/comments.

Allow admin to define default visibility (public, unlisted, private) for new posts in a board. Also allow changing post visibility, so you can use it as a moderation feature.

Linear is mostly a place to track work but as a b2b biz it's still a repository of a fair degree of signal. CSMs etc jump on client calls and have bugs/issues etc that they want to log and they get raised as tickets in Linear. So the use-case here would be pulling that data into Canny so it can be synthesized and monitored alongside requests/issues being logged directly by customers in-app or via intercom. So we have a complete system-wide view of customer needs.