…
We would like the ability to refer back to (backlink) to a post in another workspace. We should be able to backlink to multiple posts. Backlinks could essentially work like "insights" that feed into an actual feature. Where each backlinked post = insights that validate the parent
Feature2
…
Description: Add a per-announcement (or global) setting that lets admins disable the "already seen" tracking currently handled via sleekstorage (with cookie fallback), so a specific pop-up or announcement can be shown to a visitor on every visit/session rather than only once. Pro
Feature0
…
Description: Add write tools for voting to the MCP server: create a vote, update a vote (e.g. upvote → downvote), and remove a vote. Each should identify the voter by user_id or email — ideally both are accepted, with email resolved to an existing user (and a clear error when no
Feature0
…
Description: Assign a feedback post to your own coding agent — Claude Code, Cursor, GitHub Copilot, or one you built yourself — and get an implementation plan back, attached to the post as a document. You connect your own agent account, so the work runs on the agent you already p
Feature0
…
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
Feature0
…
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
Feature0
…
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
Feature0
…
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
Feature0
…
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
Feature2
…
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
Feature0
