Backlog
475Under consideration
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).
Manage workspace settings through API and MCP
Create, edit, and delete Request labels, categories, statuses, and form-field definitions through the API and MCP, including field options and required-field settings. This would let teams and AI agents set up and maintain their workspace configuration without repeating the setup manually in the dashboard.
Export banner viewer data for cross-referencing purchases
Provide an export feature for banner statistics that extracts the users who interacted with or viewed a banner, so the data can be transferred to an external database or file. Copying data manually is not viable at the scale of thousands of tracked users. The goal is to correlate banner viewers with purchase data to measure conversion after a communication campaign.
Sync Private Comments to Jira Tickets
I would like the ability to send private comments from Featurebase posts to the linked Jira tickets. This would help consolidate all relevant internal communication within Jira.
Manage and create Roadmaps through API and MCP
Create and manage Roadmaps through the API and MCP, including their columns, filters, and visibility. This would let teams and AI agents configure Roadmaps and keep them up to date from their own tools without manually editing each Roadmap in the dashboard.
Set conversation attributes when creating a ticket
Allow conversation attributes to be chosen at the moment a new ticket is created, rather than only after the ticket exists. Currently the ticket must be created first and then located again to fill in the attributes, which doubles the work when the information is already known at creation time. The creation dialog (see attached screenshot of the Create new ticket view) offers no place for these attributes even though there is room for them. The selection must expose the existing conversation attributes so the values link to the current attribute set; adding a separate new value that does not integrate with the existing attributes would not solve the problem.
Add 'currently viewing' to feedback posts
I am requesting a feature to display who is currently viewing a feedback post within the feedback module. This functionality is currently available in the Support inbox but not for feedback posts. Our team experiences duplicate effort, with approximately 5 out of 400 weekly feedback posts last week receiving similar replies from multiple agents. This leads to wasted agent time and a suboptimal user experience. Implementing a 'currently viewing' indicator would allow agents to avoid posts being actively worked on.
Auto suggest known fix for recurring issues before creating a new ticket
When a repetitive problem comes in that we have already seen and solved before, we would like the system to automatically suggest the known fix to the person reporting it, instead of a brand new ticket being created that our team has to triage from scratch again. Ideally this could even resolve or close the ticket automatically once the known fix is suggested, saving our team time on repeat issues. Raised during a demo call. We are a franchise network handling IT support and feedback for around 500 to 600 internal franchise users, and want automation that reduces repeat manual triage.
Restrict teammates to specific brands in multi-brand workspaces
In a multi-brand Enterprise workspace, allow admins to restrict which teammates can reply to conversations for a given brand. For example, some teammates should only be able to access and reply to Brand A conversations, while others can be granted access to Brand A and Brand B. Today, Assignments controls routing (who a conversation gets assigned to) but does not enforce a hard restriction on who is allowed to reply to a given brand's conversations. Teammates without brand access can still reply. Requested by a prospect running a white label, multi-brand support setup on behalf of their own customers, where different support staff should only be able to touch specific brands' conversations.
Google Meet integration
Support a native integration between Google Meet and Featurebase. Capture insights, action items, and feature requests from Google Meet calls and log them into Featurebase as structured feedback, linking customer conversations to the roadmap.
Planned
47Committed and queued
Allow search in rejected, on hold and completed posts
The search feature doesn’t allow users to search for similar posts if they are already completed, rejected or on hold. It searches only in the opened posts leading to tons of people asking for the same thing even if already completed because only open posts are considered.
[HubSpot] Subscribe salesperson to the ticket with the user
When sales subscribes prospects to Featurebase posts through the HubSpot integration, they should also be subscribed to the updates themselves to receive notifications when the request is resolved.
Automatic comment translator
Similarly to automatic feedback translations, translate users comments into their native languages.
Make custom fields translatable
Custom field labels can not currently be translated like the rest of the forum.
Search post in the user language
When the user is creating a post or searching by it, it'll not find the post unless the user search in the original post language (which they usually won't do) The video below demonstrate the problem to find the post: As you can see, the user search exactly the same word they see in Spanish ("Reacción"). However, since the post was created in English, they won't find it unless searching for "Reaction”
Email field in the feedback form (that populates for users)
Option to ask customers their email with the custom fields form, that would automatically populate the users data.
Filter the feedack for which I apply the AI deduplication
As a PM I use a specific view based on a custom field to filter the feedback of the features I own. I want to be able to find duplicates with AI only on my view of feedback. Today the AI will always look for all feedback.
Allow for customizing the title of the feedback widget board form
The title just defaults to whatever the board’s name is, but it’d be nice if we could customize it. Ideally when using the SDK to open the widget, but via the settings would be nice, too.
Support Oauth 2.0 flow for SSO
We are currently integrating Featurebase into our platform and noticed that the current Single Sign-On (SSO) implementation supports JWT-based authentication. While this works well for simple setups, we would like to request OAuth 2.0 support as an additional SSO mechanism. Use Case: Our organization uses Ory Hydra as an OAuth 2.0 and OpenID Connect provider to manage authentication and authorization for our users. This allows us to centralize identity management and enforce security policies across all applications. However, since Featurebase relies on JWT tokens passed directly via query parameters, integrating with Hydra requires additional middleware to bridge the gap between OAuth and Featurebase's JWT-based SSO flow. Challenges with Current Setup: Additional overhead to validate OAuth tokens and transform them into Featurebase-compatible JWTs. Loss of native OAuth 2.0 features like refresh tokens, token introspection, and revocation. Difficulty in managing multi-app authentication workflows within a single identity provider. Feature Request: We would like Featurebase to support OAuth 2.0 and OpenID Connect as an alternative SSO mechanism, allowing us to: Configure an OAuth authorization endpoint for login. Accept an Authorization Code or Implicit Flow for token exchange. Validate tokens via a JWKS URI or Introspection Endpoint. Provide support for Scopes and Claims Mapping to handle user attributes. Seamlessly redirect users after authentication, similar to the current JWT-based flow. Benefits: Simplifies integration with modern identity providers like Hydra, Auth0, Okta, and Keycloak. Enhances security through native OAuth 2.0 mechanisms. Allows better scalability for enterprises managing multiple applications. Priority: While the current JWT-based SSO is functional, adding OAuth 2.0 support would significantly streamline our authentication process. We would appreciate it if this could be considered in the upcoming roadmap.
Email integration for feedback
Add an option to add feedback by sending it in via email. I.e. the subject line becomes the title and the body the text of the feedback post.
Next up
4Committed and queued
Automatically capture feedback from Slack with AI
Have a “Featurbease agent” you can @mention in Slack discussions that automatically creates issues (or add insights to existing issues) based on the conversation’s context. Or even a Slack agent that continuously monitors a #feedback channel and automatically identifies and submits feedback to the Featurebase board. If there’s already a post about an issue, it could add it as an insight to the existing post.
Allow End-Users to Filter and View Their Own and Company-Only Feature Requests
End-users on the public portal should be able to view and search feature requests submitted by themselves (author-only) or by others within their company (company-only). This would enable customers with multiple contributors to easily see what they or their organization have already requested, without requiring admin dashboard access. Filters for Author and Company, along with search across these scoped views, should be available to logged-in end-users to improve visibility, reduce duplicate requests, and provide clearer feedback ownership.
Accordion element cuts text with long questions
In case of longer FAQ questions, the accordion element cuts off the text:
Integration with Linear Customer Requests
https://linear.app/customer-requests
In Progress
2Actively being built
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.
Multi-brand support for the Feedback Portal & Updates
Support multiple brands within a single Featurebase workspace and portal.
Done
312Recently shipped
Audit log / change history for feedback posts
Requesting a per-post activity log showing who changed what and when: status changes, merges, edits, deletions, assignee changes, etc. Important for larger teams that need accountability and traceability over how feedback is triaged and prioritized, especially with multiple admins working the same boards.
Grain integration
Support a native integration between Grain and Featurebase. Automatically turn customer call and meeting insights captured in Grain into structured feedback and feature requests in Featurebase, so what customers say on calls feeds straight into the roadmap.
Let admins select a suggested duplicate during post creation to auto-upvote, instead of merging after the fact
When creating a new post, Featurebase already surfaces similar existing posts in real time. Right now, clicking one of these suggestions just navigates you to that post instead of associating your new comment/vote with it, so you still need a separate "Merge posts" step afterward to avoid a duplicate. It would be great to select a suggested duplicate right in the creation flow (similar to how the Slack /featurebase command lets you grab an existing post and add your comment to it in one step), so internal team members submitting on behalf of a customer don't have to remember to go back and merge later.
MCP support for adding/managing post upvoters (voting actions)
When consolidating feedback gathered from GitHub, Slack, and other outside channels, we'd like to add multiple upvoters to an existing post in one go (e.g. 5-20 people who mentioned the same request elsewhere) via the Featurebase MCP server. Today the MCP server only exposes read/search actions for posts and users - there's no MCP action to add or manage upvoters on a post. Requested a write action (ideally supporting bulk/multiple upvoters at once) so this can be done without manually adding each person one by one in the dashboard.
Allow admins to answer follow-up questions on users behalf
When admins add voters or commenters on behalf of users, they currently cannot fill out follow-up questions (like importance fields). This makes it impossible to track that User A sees the feature as 'nice to have' while User B considers it 'blocking'. Enable admins to complete per-user metadata when adding people to posts.
HubSpot sync options missing
HubSpot integration modal still shows article reference instead of Contact/Company sync configuration options. Only displaying "Remove HubSpot" and Enterprise reference to Deals sync.
AI Post Enhancement
I want to use AI to enhance posts to make them more robust and clear. This would help users write better feedback by automatically improving the clarity and detail of their submissions.
HTML lang tag not set correctly on initial page load - Help Center
As you can see in the video below, when first loading any page in the Help Center, when a non-english locale is selected (e.g. French) the html lang tag is set to lang="en". However, when navigating to another page, the lang tag is set correctly to lang="fr". If you reload the page, it goes back to lang="en". We noticed this, because most of our customers use screen-readers, and for some screen-readers, the speech synthesis is based on the html lang tag value. It is quite uncomfortable to have a digital english voice read to you in french !
Filter posts by follow-up question answers (e.g., Importance/Urgency)
I want to be able to filter the main post list based on the answers given in follow-up questions. Specifically, I need to identify posts where at least one customer has marked their vote as "Essential" or "Blocking". Currently, this data is only visible at the individual vote level, meaning critical adoption blockers are buried unless we manually open every post.
Jira Sync Rules Persist After Project Disconnection
After adding sync rules for a project and then removing that project, the rules disappear from the UI but seem to linger in the system, causing incorrect Jira integration behavior. For example, all ideas might still sync to a specific Jira board even when they shouldn't.