Feature Requests

When trying to submit a feature request here on "The Canny Boards," it's extremely hard to find related feature requests. Even with a fairly long and specific search string, the results returned are way too numerous and not very closely related. Would love to see: (1) Improved search result relevancy and/or relevancy score (80% match vs. 5% match) (2) Non-infinite scroll of results list (3) "Sort by" top vs. new vs. trending setting persistent as you search keywords (it appears to be one or the other, EITHER sort or search) (4) When creating a request, category search working (I think it does not function) (5) Better documentation about how to effectively search or/join/submit feedback --- The more I type here, the better the search results are getting in the table below, but that's very counter-intuitive to me, that I need to fully draft my own post before finding out that there is a good match and I really shouldn't post it at all. At this point I'm invested! (6) More moderation on these boards, with ClickUp employees dedicated to linking/merging similar/duplicate requests so there aren't 36,030 records to work thorough for every user of this board. (7) More assistance from chat support people in finding the most relevant place to post feedback. When I asked for help I was given suggested feature requests I could upvote but they weren't good recommendations that matched what I was getting at, which suggests to me that either (a) The chat support reps ALSO find it very challenging to search these boards or (b) Perhaps because the teams are separated, the support people are not very invested in the user feedback/development roadmap process and don't mind that the feedback here is so sprawling/hard to search that it's hard to use.

There is a lot of talk and anticipation on Clickup 3.0. The hype was there, the reality isn't yet. That's all fine. The main reason why people seem so eager is that the currently stability of the program is lacking. My enthusiasm has also largely gone because I'm introducing it in my company and I have reported several issues already. I understand we have to await Clickup 3.0 and the long awaited upgraded backend, however I would propose that Clickup would introduce a bug bounty program. This would be a real motivator to focus more attention to actually creating the best product instead of promising :) I have no clue how that would best look like but I can imagine you could earn as first reporter a quarter worth of free license and second reporter a month. This way there is a real need to focus on reducing bugs. Other ideas welcome, I was just wondering how Clickup can really benefit the pro-active nature of most of its customers plus grow into the product it should be. This is a lot of potential but it really needs to polish up a bit.

Within feedback.clickup.com , there should be a way for me to view all my posts submitted feature request posts.

This is not for the Clickup product, but for the actual support / bug report process. Usually when I report a bug or request support, I'll get a ticket number with a specific subject line so that it's easier to keep track of all my requests. A step further: some places allow you to see all your open tickets in one place. Currently all my bug reports come back with a subject of: "Your ClickUp Bug Report 🐛" Makes it very hard to keep track of my various requests.

Right now it is very cumbersome to report reduced/degraded performance. It has an impact on our productivity and so, to us at least, it doesn’t feel like it is treated with any form of urgency on Clickup’s part. You have to use the “chat” function, to ultimately submit a ticket. Which all in all took close to 5 minutes. Here’s an idea: How about a button on the status page ( status.clickup.com ) titled “report reduced performance” or something like that? Sure, if after that the automated system still asks a bunch of basic questions, I get it. But having to search for a way to report and then still jump through a bunch of hoops … The impact of any outage can be high, as many use Clickup for documentation, for dev sprints, … It can grind dev work to a halt. Having a faster way to report an outage would be great. Especially if we can get the impression that it is treated with priority and not with the rest of support tickets. Perhaps the nature of the ticket means that it is, how would you know? And that is part of the problem. If there’s a “report reduced performance” button, and that starts some kind of counter on Clickup’s end, or even on the status page, that increases the urgency as more reports come in, that would at least give the feeling that customer’s reports of reduced performance are being dealt with with the highest priority. Not saying they aren’t at the moment, but the clumsy reporting method and the lack of any indication it will be dealt with with the highest urgency, don’t help.

It would be helpful to add a feature to turn off the background music in the intro video, or change it to something less abrasive. For those of us with sensory issues, the thumping hip hop beat makes it difficult to hear and process the words. I couldn't watch it all the way through.

Understanding how users interact with your platform can feel like piecing together a puzzle, but that’s exactly what feedback boards are built for. They offer clarity, structure, and a direct line to user sentiment. When people share their thoughts, ideas, or frustrations in a space designed to listen, everyone wins. One great example of this is how platforms like https://pearllemonexperiences.com/brand-activation-agency/ extend that same philosophy to brand experiences, merging purpose with design. A well-designed feedback board feels like a conversation, not a survey. It’s an invitation: “Tell us what you need, what’s working, what isn’t.” Each post, vote, or comment is a piece of insight that helps teams focus their efforts where it truly matters. As users submit feature requests or report bugs, the board captures their voice, transforming scattered messages into something visible and organized. It becomes easy to see which ideas resonate most, guiding decision-making and roadmap planning with real data. Transparency plays a key role in building trust. When users can view status updates, whether something is planned, in progress, or completed, they know their input matters. This visibility helps foster loyalty and engagement because people feel heard. For teams, feedback boards aren’t just listening tools. They’re bridges between product strategy and user reality. Prioritizing requests based on votes and discussions ensures resources are allocated smartly. Development becomes more user-centered, and outcomes become more impactful. The structure of these boards often mirrors the structure of a good user experience. Categories group feedback by feature area, statuses show progression, and discussion threads enable deeper exploration of ideas. This thoughtful layering transforms raw feedback into actionable insight. When implemented well, feedback boards don’t just inform product development, they invite collaboration. Users become part of a community, contributing to the product’s growth story. Their participation becomes part of the product’s DNA, not just a one-off survey. Ultimately, feedback boards demonstrate that product development is never a solo journey. It’s a collective journey empowered by tools that listen, surface, and respond to real user needs. When companies value this exchange, they foster a cycle of continuous improvement and community involvement. Like any successful experience, feedback boards succeed when built with intention, clarity, and respect. They ask for input and respond with action. And in that response, users find reason to stay engaged, invested, and excited for what comes next.

As a sysadmin and the enterprise owner of the platform I can only see my own open tickets. There is apparently no way for a sysadmin or sysowner to review all open support requests.