Feature Requests

Need a chat window like LinkedIn to always have chat available when using Clickup. It happens most of the time that i want to interact with a person while working on a doc/ticket and it becomes very difficult to switch between chat and the working screen again and again

It would be helpful to allow users to create or book a meeting room within a channel, similar to how virtual rooms work in other collaboration platforms. Proposed functionality: Create a persistent meeting room attached to a channel. Schedule or "book" the room for a specific meeting. Allow participants to join through the same room link each time. Keep the room open for the duration of the meeting. Allow hosts to end the meeting early or automatically close the room after the scheduled end time. Show room availability and upcoming bookings within the channel. Benefits: More organized recurring meetings. Easier meeting access since links remain consistent. Better alignment with team collaboration workflows. Reduced confusion around temporary meeting links.

I would like ClickUp to add the ability to delete channels that are no longer needed. I use channels in ClickUp for each project to discuss tasks, share progress, and brainstorm ideas. However, when test channels, channels for completed projects, or channels created by mistake continue to remain in the workspace, the channel list becomes harder to organize. For example, I sometimes create channels such as “Test Channel” or “Temporary Campaign Discussion” when trying out a new workflow. Later, once the official channel name or operation method is decided, those test channels are no longer needed. If I could delete those channels, unnecessary information would not remain, and team members could more easily find the channels they actually need to use. As a real example, I once created a channel for a short-term project, but after the project ended, the channel continued to remain in the workspace. Because several channels had similar names, some members accidentally posted in the old channel, and it became unclear which channel was currently active. If channels could be deleted, this kind of confusion could be prevented, and the workspace could stay clean and organized. Of course, to prevent accidental deletion, it would be helpful to have a confirmation screen before deletion, an option to allow only admins to delete channels, and a way to restore deleted channels for a certain period of time. Also, if users could choose between archiving and deleting channels depending on the situation, channel management would become even more flexible. With this feature, I could more easily clean up unneeded channels, and the entire team could access the right information without confusion. I think this would be especially useful for teams that manage many projects or temporary experiments within ClickUp. ClickUp is an excellent service that brings task management, documents, chat, and project visibility together in one place. It helps me organize my daily work and collaborate smoothly with my team. I truly appreciate the ClickUp team for continuing to improve such a wonderful product. Thank you very much for all your hard work.

I would like ClickUp to allow Channels that were created without being linked to a List or Folder to be linked to any List or Folder later. In the early stage of a project, I often do not yet know which List or Folder a Channel should belong to. Because of that, I would like to start the conversation as an independent Channel first, and then connect it to the appropriate List or Folder once the project structure becomes clearer. For example, when I start discussing a new marketing initiative, I may first create a Channel called “New Campaign Discussion.” At that point, I may not yet know whether it should be connected to a List for “Ad Operations,” “Landing Page Production,” or “Social Media Posts.” However, as the discussion progresses, I may realize that the conversation is mostly related to the “Landing Page Production” List. In that case, being able to link the existing Channel to that List later would help me naturally connect the conversation with task management. As a real example, I once created an independent Channel for brainstorming campaign ideas, and later realized that the discussion was directly related to a project under a specific Folder. However, because I could not link that Channel to a Folder or List afterward, I had to manually move information or create a new Channel. This broke the flow of the conversation and made it harder for team members to find the relevant context. With this feature, I could start conversations flexibly in the early stage of a project and organize them into the correct ClickUp structure later. I think this would be especially useful for planning, development, marketing, and other workflows where the topic is initially unclear and the proper management structure is decided afterward. ClickUp is an excellent service that brings task management, documents, chat, and project visibility together in one place. It helps me organize my daily work and collaborate smoothly with my team. I truly appreciate the ClickUp team for continuing to improve such a wonderful product. Thank you very much for all your hard work.

It would be helpful to have an option to enable or disable auto-capitalization in Chat and Docs Currently, users must manually capitalize the first letter of sentences and proper nouns. An optional auto-capitalization setting would improve typing efficiency, readability, and consistency.

In Slack Huddles, when someone shares their screen others are able to "draw" on the screen being shared using the pen tool. This is extremely helpful for teams working remotely.

Admin should have the possibility to set this, in order to prevent users to chat and then delete messages (you can do it in Slack). To me, this feature is essential.

i need to get github , sentry.io events into chat rooms

I'm the project manager and like to keep everything connected. Sometimes, people send messages in the channel that should be replies in a thread. I'd like the ability to move those messages to a thread once they have been posted.

Currently, our team sends several standardized messages in Chat channels daily (e.g., Daily Standups, Weekly Handover reports, or specific Check-in checklists). Manually typing these out or copying/pasting them from an external Doc is a significant friction point and leads to inconsistent formatting. I would like a native way to create and save Message Templates specifically for the Chat view. Key Functionality: Template Library: A place to store "Canned Responses" or snippets. Quick Access: Use a slash command (e.g., /snippet or /msg) or a "Template" icon in the chat bar to insert the text instantly. Dynamic Variables: Ideally, allow simple variables like @Today or @Me to populate automatically. Formatting Support: Ensure the template preserves Markdown (bolding, lists, and dividers). Why this matters: This would bring Chat on par with Task descriptions and Docs, allowing teams to maintain a "Single Source of Truth" for communication styles without leaving the conversation.