Feature Requests

Please search first before posting to help others find and vote for your idea!
SLOW again!!
I don't have a large database to manage in ClickUp, or any automations worth speaking about, or fancy templates. I'm just a simple power user. Some of us spend enormous amounts of money on our gear to overcome performance issues with localized applications when they aren't optimized. But we have NO power here. There is NO reason in 2025 with ClickUp's success that this platform needs to be so slow. It was great last year when I was in it every day for hour working with AI, creating CU docs, multiple user types, diagrams, etc... this year, it's been chill, and it take up to 10 seconds to load the app UI on every computer. This is on a browser and the desktop app. M1 Max MBP and Linux (main daily): Hardware Specifications • CPU: Intel Core i9-12900K (24 cores, 5.2GHz max, 12th Gen) • RAM: 48GB (47999MiB) • GPU: NVIDIA GeForce RTX 3090 Ti (23GB VRAM) • Samsung SSD 990 PRO 1TB NVMe • 2x Samsung SSD 980 PRO 2TB NVMe in RAID • WDC WD80EMAZ 7.3TB HDD • Motherboard: EVGA Z690 DARK KINGPIN • Dual Intel I225-V 2.5GbE Ethernet Controllers • Network Performance: 2350.85 Mbps down, 13.93 ms latency Software Environment • OS: Arch Linux (Kernel 6.14.9-zen1-1-zen) • Desktop Environment: KDE Plasma (6.3.5) with Wayland • Display Server: X.org with Xwayland 24.1.6 • Shell: ZSH 5.9 • Browser: Google Chrome 137.0.7151.68 • Terminal: Warp Terminal • ClickUp 3.5.87 Graphics Stack • NVIDIA Driver: 570.153.02 • CUDA Version: 12.8 • APIs: OpenGL 4.6, Vulkan 1.4.313, EGL 1.5
0
·
Support & Non-Product…
feature request / suggested improvement : can we get better bug tracking / updates? (#1788390)
Howdy, team ClickUp / Support; as you will be aware, we currently have numerous open issues filed & pending resolution with your team. While we appreciate the option to theoretically check on progress per your ChatBot ("Check status of reported bug (CLK)"), the 'information' returned routinely is abysmally uninformative. It's just always the same boilerplate payload, conveying absolutely nothing about the actual state of the individual case/s: [Image] That's rather frustrating, to put it in the mildest possible terms. Consequently, if it's not already somewhere on your wishlist submitted by other users, we'd very much welcome an improved issue tracking more similar to how you're already treating feature requests (on canny.io ). Specifically, we would like to be able to see at any given time ... : * the actual stage an individual issue is currently in at your side, * the place in the queue it is at (like "{n} cases ahead before this one" or something similar, to gain some idea as to when it might actually get addressed), plus, in an absolutely ideal world * a list of cases pending resolution for our workspace – so we don't have to keep track of open issues manually ourselves. I may be jumping wildly to conclusions here, but given the platform you're running it should be a simple matter of sharing a properly filtered list with its respective stakeholders, should it not? Thank you for your esteemed consideration of this suggestion. Best –
0
·
Support & Non-Product…
Load More