Help us build Sleekplan.

When users try to use @ -mentions in comments on the feedback portal or the in-app widget, the mentions don't work properly. This affects the ability to notify and engage specific team members or other users in comment threads.

Description: Privacy is currently set on the category, not on the post. To keep one item out of public view you have to move it into a private or segmented category — which changes what kind of request it is, and applies to everything else in that category too. This request adds

Description: Sleek Mate ships with a fixed set of built-in skills — repeatable playbooks like the weekly product review, duplicate cleanup, PRD drafting and changelog composition. They are the same for every workspace and you cannot add to them. This request is to let you write y

Description: Today a webhook is a single global subscription: you add a URL and it receives every event your workspace produces — new posts, comments, votes, subscriptions, users, changelog entries, survey and satisfaction responses. There is no way to say "only tell me when a po

It would be useful if Access & Privacy settings could be configured independently for each section of a Sleekplan portal, rather than applying one privacy setting to the entire portal. Our use case We have different audiences and purposes for different parts of our portal. Fo

It would be useful to extend Domain Restricted portal privacy so that access can be granted based on an email domain suffix, rather than requiring every individual domain to be added. Our use case We work exclusively with organisations in the education sector and have around 60 c

Description: As a product manager, I want a two-way Jira integration that generates a PRD from an idea (with attached/linked customer feedback), maps idea fields to Jira fields on create/update, and syncs Jira statuses and updates back to the idea so that I have end-to-end tracea

Description: When creating a jira integration i would like the abilty to map the Sleekplan fields to the jira card and make it more streamlined for the two system interations Purpose: to ensure that when we are developing and resolving issues that these are sharing the same infor

Summary Calling the changelog update endpoint with draft: false and a future scheduled Unix timestamp does not schedule the entry correctly. Instead, the entry enters a broken state: it stays retrievable via the API (not live, enabled: 0), but disappears entirely from the dashboa

Description: Directory sync currently covers frontend portal users only. Admin (team member) accounts still have to be added and removed manually in the dashboard. This request is to extend directory sync to the admin area as a second, independently configured sync, not as an ext