Please tell us what we can do to make Featurebase the best product for you.
Use Fibi AI as an automatic feedback moderator
I would like Fibi AI to automatically moderate customer feedback in a way similar to the Auto Moderator bot used in the subreddit community. This could help review and manage incoming requests with less manual effort.
Choose which calls sync from call recorder integrations
Let admins control which calls sync to Featurebase from connected call recorders, instead of importing every call the connected account can access. For Grain, allow selection of specific teams or an equivalent access scope. Provide clear controls similar to selecting folders in Granola, so only the intended customer calls are imported and private internal calls stay out of Featurebase. The selected scope should apply to both transcripts and any feedback extracted from those calls.
Require all three Impact answers before upvoting
Allow admins to require customers to answer importance, frequency, and urgency questions before their upvote is saved. Today, customers can vote without providing these ratings, leaving teams with requester counts but incomplete Impact data for prioritization.
Open matched posts in a new tab from the insight composer
Allow users to open the matched post in a new tab without losing their insight draft, so they can read the full post and confirm it’s a duplicate before adding the insight.
Show full descriptions and custom fields in request picker previews
The target picker preview shows a shortened description and no custom fields. Showing the full description and relevant custom fields would help teammates compare requests before merging or adding feedback as an insight, without opening each request separately.
Show whether Jira status changes trigger customer emails
When Jira changes a request’s status, the request view should clearly show whether a customer email was triggered or skipped, including when notifications are disabled in the matching sync rule. The send icon and count currently leave this unclear. Distinguish a triggered notification from confirmed delivery.
Show metadata in the source item view
When admins open a source item from a request’s Insights tab, they can see its title, body, author and creation time, but cannot access its metadata. Allow admins to view the original source item’s metadata from this view, using the existing permission checks.
Allow new comments on merged requests
Keep the original request’s comment box available after a merge, so the team and users who can access it can start and continue discussions there - even when they cannot access the kept request. Replies to existing comments do not fully cover this need, especially when the original request has no comments. Preserve each request’s access restrictions.
Company-level request submission instead of individual users
Ability to create requests on behalf of a company not an individual user
Add a toggle to disable request creation from Linear
Add a separate toggle in the Linear integration settings to stop Linear issues and projects from creating new Featurebase requests, including items carrying the Featurebase label. Turning it off should preserve existing links and status syncing according to the configured rules. This would prevent unwanted requests across workspaces sharing a Linear team without requiring customers to remove their sync rules.
Category default blocks public visibility for individual requests
With Category access = Everyone and Default request visibility = Author only, the individual request dropdown offers only Author only and Internal. It does not offer Everyone. The default should apply to new requests. The team should still be able to make one request public without changing the default. The default should apply to new requests. The team should still be able to make one request public without changing the default.
Checkbox form field: option to be checked by default
Let admins set a Checkbox custom field on the request form to start checked. Teams with DPA or consent text want the box pre-selected, and users can still untick it. Today the Checkbox field only has "Require checking" (the user must tick it before submitting); it always starts unchecked.
GitHub integration: board-level sync rules and per-board repository routing
Bring the GitHub integration in line with Linear and Jira: let each Featurebase board (category) route to its own GitHub repository, and let sync rules be scoped per board. How it works today Automatic push uses one repository for the whole workspace. It can be limited to selected categories, but every pushed post lands in that single repository. GitHub sync rules map a GitHub issue state to a Featurebase status. A rule has no board field and no repository field, so rules cannot be scoped by board or by repo. The repository is only selectable at push time, on a manual push. A post can end up linked to issues in several repositories that way, one push at a time. One GitHub App installation per workspace. Requested behaviour A repository field and a board field on GitHub sync rules, so each board can drive its own repository and its own status mapping. Automatic push that resolves the target repository from the post's board instead of from one global setting. Same shape as Configure Linear integration Sync Rules per board and Jira integration sync rules with multiple projects, both already shipped. Why it matters Raised by a prospect running roughly 15 products, each with its own engineering team and its own repository. Without board-to-repository routing, only one team gets hands-off automatic sync and every other team has to push manually, or the company has to split into separate Featurebase workspaces purely to work around the integration. Related: Support for multiple GitHub organization integration, Advanced GitHub Integration Mapping (Title, Body, Board to Labels).
Support product tours on mobile devices
Extend product tours to run on mobile browsers. Tours currently work only on desktop, which excludes mobile-first user bases from onboarding and in-app guidance flows.
Manage Request prioritization, visibility, and status updates through API and MCP
Read and update Impact ratings and Value/Effort scores through the API and MCP. Include the importance, urgency, and frequency ratings used to assess customer demand. Also allow changing whether an existing Request is internal or hidden from the Feedback Portal. This would let teams automate prioritization and control which Requests are shared with customers. Also support publishing custom Request status updates through the API and MCP, with formatted text, links, and images. Allow sending an update when changing a Request's status or for its current status, with an option to notify Requesters. The message should appear as the same pinned, status-labelled update used in the dashboard and be included in the status-update notification. Currently, the public API and MCP can change a status and send the default email, or create a regular comment, but cannot publish a custom status update. This prevents teams and AI agents from completing the full update workflow.
Filter a post's voters by company attributes
I want to filter the voters of a single post by company attributes such as industry or company size, directly in Featurebase. Today the only option is exporting the voter list to CSV from the post and then filtering it in Sheets or Excel. Product research teams pick voters for discovery calls and beta tests every week (for example only construction or cleaning companies out of 300 voters), so this manual step slows them down.
Show full request titles by default
Show the full request title by default in the request view instead of truncating it to five lines.
Apply board access permissions to posts awaiting approval
I would like an option to let users with access to a board view posts while they are awaiting approval in Triage, using the board’s access permissions. This would allow members of the author’s company to access company-only posts before an admin approves them.