Feature Requests

Please search first before posting to help others find and vote for your idea!
Text Wrap / Multi-line Task Name Display in List View and Table View
Feature Request: Text Wrap / Multi-line Task Name Display in List View and Table View Problem: When task names are long (especially common in non-English languages like Japanese, where task names tend to be longer than English equivalents), the task name gets truncated in both List View and Table View. Users have to hover or click into each task just to read the full name, which significantly slows down scanning and reviewing. Proposed Solution: Add a "Text Wrap" or "Row Height" option for the task name column in List View and Table View that allows: Auto-wrap: Task names wrap to 2 or more lines based on column width, similar to how spreadsheet applications (Excel, Google Sheets) handle cell content. Fixed multi-line height: A setting to fix the task name row height to 2 lines (or a user-chosen number of lines), so all rows display consistently while showing more of the task name. Why this matters: Project management tasks in research, government, and enterprise contexts often have long, descriptive names that cannot be shortened without losing meaning. Non-English languages (Japanese, German, etc.) naturally produce longer task names than English. Currently, Table View offers a Row Height setting, but it only increases vertical space without wrapping the task name text, making it only partially useful. This feature would dramatically improve readability and reduce the need to click into individual tasks, especially when reviewing large task hierarchies. Suggested implementation: Add a "Wrap text" toggle in Customize → Layout options for both List View and Table View. Optionally allow users to set the maximum number of visible lines (e.g., 1, 2, 3, or auto). Thank you for considering this. It would be a huge quality-of-life improvement for teams managing complex, multi-level project structures.
0
·
Hierarchy
Warning Notification When Re-nesting a Task Changes Its Home List
FEATURE REQUEST SUMMARY We are requesting a warning or confirmation prompt when a task or subtask is re-nested under a different parent in a way that automatically changes its home list. CURRENT BEHAVIOR When a task or subtask exists in multiple lists and is re-nested under a different parent task in a secondary list, ClickUp silently removes it from its original home list with no warning, confirmation dialog, or undo notification. Specifically: • Tasks: Re-nesting a task under a new parent in List B automatically removes it from List A (its home list) and reassigns List B as the new home list — without any user prompt. • Subtasks: The same behavior occurs for subtasks. Re-nesting under a new parent in List B removes the subtask from its original home list in List A. In both cases, the task or subtask is not deleted, but because there is no notification of the home list change, users believe the task has disappeared. USER IMPACT This behavior has caused significant confusion among our users, who interpret the silent home list change as tasks being lost or deleted. This erodes trust in the platform and creates unnecessary troubleshooting overhead for our team. REQUESTED BEHAVIOR We would like ClickUp to introduce a confirmation prompt or warning notification when a re-nesting action is about to change a task's home list. Ideally, this would look something like: "Nesting this task under a new parent will change its home list from [List A] to [List B]. This will remove it from [List A]. Do you want to continue?" This small change would: Prevent accidental and unintended home list changes. Give users a clear opportunity to confirm or cancel the action. Improve transparency around how multi-list task management works. Reduce user confusion and support escalations related to "missing" tasks. We hope this is a relatively low-lift UX improvement that would have a meaningful impact on user experience, particularly for teams managing tasks across multiple lists. We hope this can be considered for a future update.
0
·
Hierarchy
Load More