Feature Requests

Please search first before posting to help others find and vote for your idea!
Treat Lists as First-Class Items for Cross-Department Portfolio Tracking
Problem ClickUp currently lacks a flexible way to manage and track portfolios of distributed projects or initiatives while maintaining custom attributes and automatically aggregated progress. Our use case: We have an Initiative Overview list that tracks approximately 40 company-wide initiatives. Each initiative is managed independently in a department-specific Space/List, where teams execute their work. In the central overview, we want to track: Progress: Automatically calculated from the tasks within each linked initiative list (e.g., 18/25 tasks completed, 72%) Status: Overall initiative health and execution status Custom Fields: Strategic goals, stakeholders, owners, priorities, budgets, etc. Reporting: Centralized dashboards showing progress across all initiatives We have the exact same challenge with customer onboarding projects: Each customer has a dedicated onboarding list, while a central controlling list tracks commercial and operational information across all onboarding projects. Why Existing Functionality Isn't Sufficient Portfolio Views are a step in the right direction, but they don't offer the flexibility of regular tasks, particularly when it comes to assigning arbitrary custom fields and managing rich project metadata. Relationships and Rollups are powerful, but they operate at the task level. We cannot create a relationship to an entire List and roll up its aggregated task progress. This forces us to maintain parallel tracking structures, manually update progress, or introduce unnecessary workarounds. Proposed Solution We see two possible approaches: Option 1: Allow Relationships to Entire Lists (Preferred) Extend ClickUp Relationships so that a task can reference an entire List, not just another task. For example, an item in our Initiative Overview could link directly to the corresponding department initiative list. The overview task could then automatically display or roll up: Total tasks and completed tasks Percentage of tasks completed Overdue and blocked tasks Milestone progress Other aggregated metrics from the linked list All existing task-level capabilities, such as Custom Fields, ownership, descriptions, statuses, automations, and dashboard reporting, would remain available. Option 2: Make Lists First-Class Portfolio Objects Alternatively, substantially expand Portfolio Views so that Lists behave more like regular tasks. A List should support: Arbitrary Custom Fields, directly assigned to the List Owners, stakeholders, goals, and other metadata Custom statuses and health indicators Progress metrics calculated from its underlying tasks Full support in dashboard widgets, filtering, grouping, sorting, and automations Conceptually, a List would become another type of parent item, with its own metadata and aggregated progress, rather than merely a container for tasks. Expected Outcome We want to build centralized, fully customizable portfolio trackers without moving or duplicating the underlying work. Teams should continue working in their own Spaces and Lists, while leadership, project management, and controlling can track dozens or hundreds of distributed initiatives or customer projects through one central view. The key requirement: Combine the flexibility of a regular ClickUp task (Custom Fields, relationships, automations) with the aggregated progress and hierarchy of an entire List. This would be a major improvement for strategic initiative management, customer onboarding, PMOs, cross-department project portfolios, and enterprise-wide reporting.
0
·
Fields, Formulas,…
Organizing Custom Fields into Groups and Custom Fields Visibility at Task Level
*Note: this request concerns organizing custom fields into groups, not grouping views by custom fields. Currently we have the ability to set custom fields at the Space > Folder > List levels, but it would make sense, and be immensely helpful, to extend that capability one level down to the task level as well. One idea – and perhaps the easiest to implement - would be to simply allow organizing of custom fields into groups with the ability to collapse groups (e.g., unused groups) at the task level. Setting custom fields at the space level, with the ability to customize at the folder and list levels completely makes sense, but there are, in many cases, a variety of task types at the list level that don't need to share the same custom fields inherited from the list where they live. To give an example, for my industry I track real estate transactions (purchases and sales) on a per client basis, with the client name at the folder level, plus specific real estate transactions at the task level, in addition to other types of information related to the client and their history as a current client. After fairly extensive experimentation and trial and error, I have 4 types of tasks (indicated by status) that are tracked at the folder (client) level: Client Data (for general client info prior to making a purchase or sale) Transaction Data (for specific purchases and sales to track contract terms and deadlines) Tour History (for logging a history of properties a client has toured) Offer History (for logging offers to purchase, made or received by the client depending on if the client is buying or selling a home) Because of the extensive data related to a real estate transaction that needs to be captured (to track contractual terms and deadlines, in addition to performance data for the team dashboard), the list of custom fields is pretty long. But we don't need to see that full list for the other three types of tasks that are being tracked at the folder level. It's not a deal breaker, as custom fields is largely what makes CU a viable alternative to other platforms like Airtable, but it does add a layer of clutter and perhaps complexity that just doesn't need to be there in many cases. Here's a loom video showing how my list of custom fields displays on a task (the list is too long to take a screenshot): https://www.loom.com/share/87b6d1edd6e644c69bc6afb666a51735
79
·
Fields, Formulas,…
·
future
Load More
→