Help us build Sleekplan.

What we're building, what's next, and what just shipped.

Option to display the user full name instead of username on comments, posts etc.
Feature6
Problem: In the new admin UI, feedback titles are cut off after only a few characters — both in the Merge dialog and in the left sidebar list. When titles share a common prefix or are otherwise similar, the truncation makes them very hard to tell apart (for example, when picking
Improvement1
Problem: On the new Feedback Board it's no longer obvious which filter and sort/layout options are currently applied — these controls are hidden behind small icons. Previously the active filter parameters were clearly visible. It also now takes more clicks to change a filter. Req
Improvement1
Problem: In the redesigned admin interface, when a feedback post is open, the vote count and the Properties (Status, Category, etc.) are now tucked into the right sidebar as small elements. These are among the most important parameters for triaging feedback, and the new layout de
Improvement1
Problem: Since the 2.0 admin redesign, default fonts and icons on the Feedback Board are smaller and harder to read/find: The "Category" label is hard to read, as is the sidebar text when a feedback post is open. Key action icons are very small — e.g. the Merge icon took a long t
Improvement1
Description: Add native controls to show/hide navigation items and pages (e.g. Roadmap, Suggestions/Feedback, Changelog) in the new portal and new widget, based on the logged-in user's segment — without any custom JavaScript. Problem: Today, restricting portal/widget sections by
Feature1
When tagging a user (@mention) in the admin interface, the tag doesn't render properly in the legacy feedback portal and widget. The formatting appears broken or displays raw markup instead of a proper user mention. Suggested solution: Add proper @mention rendering to the legacy
Issues0
Expected Behavior When clicking on the view count or reaction count of a changelog entry, a detailed panel should open showing the list of contacts (users) who viewed or reacted to the update. Current Behavior Only the aggregated numbers (views, reactions) are displayed on the ch
Issues1
22
Since we use hubspot for sales & account management, having the CSAT/NPS flow into the right hubspot contact's details helps keep the full user lifecycle & info under one place.
Integrations0