Feature Requests

We cannot currently pull relationship or rollup fields into Dashboard reporting. We are using relationships & rollup fields to keep regularly updated fields up to date across all lists/tasks (i.e. if a person's manager changes and they're also on our training waiting list, we only have to change the manager in one place but the info flows through to the linked task in the waiting list as well). For example, I'd like to be able group a dashboard chart by manager to see how many people with the same manager are on the waitlist (or from the same team, in the same level, etc.).

Problem: We use Task Types as service buckets (Creative, Paid, Content, etc.). We need one Time Reporting Dashboard card that shows time tracked between two fixed dates and groups/breaks down by Task Type. Current grouping is too tied to location (ex: List) and does not support grouping time entries by Task Type within a normal client/project list structure. Value: Enables billing-grade client reporting (“hours used vs hours remaining by service bucket”), budgeting, margin tracking, and removes the need to maintain many cards per Task Type per client. Desired outcome: Add Task Type as a grouping option in the Time Reporting Dashboard card, ideally with multi-level grouping (Task Type; then Task/Client/Project; then User optional). Date ranges must be based on time entry dates (time tracked between Date A and Date B).

A Gauge Chart/ Speedometer card in ClickUp Dashboards would allow users to set a visual target dial for any type of metric so teams can instantly see how close they are to achieving a specific goal. Numeric custom fields and task counts should be able to contribute live data to this card to show real-time progress. Additionally, if the target is exceeded, the needle or dial should continue moving past the 100% mark to show over-performance. Case Examples: For Financial Targets: Summing up a money custom field (e.g. revenue) against a fixed target (e.g. a monthly, quarterly or yearly sales target). For Task Volume Targets: Tracking total completed tasks against a daily or weekly target count (e.g., tracking 15 closed tasks against a daily goal of 20).

Like publicly shared Views, please add support for publicly shared Dashboards. This is key for providing high-level visibility to people lacking guest accounts.

Currently, AI cards require manual updates to refresh their data. It would be highly beneficial to have an option to set an automatic refresh cadence for these cards. At present, refreshing the entire Dashboard does not trigger the AI cards to update. Instead, I need to switch the Dashboard to "Edit" mode and manually click the Refresh button on each AI card individually. This process is time-consuming and could be streamlined with an auto-refresh feature.

Parent tasks typically serve as containers for projects or larger initiatives. In most cases (for us anyway), the actual work is completed and tracked in subtasks. Because of this, parent tasks generally only contain high-level updates related to the overall project or initiative. It would be extremely helpful if dashboard cards could be filtered to exclude parent tasks, so that dashboards only display subtask data.

It would be great if we could get a proper Workload Card to use in Dashboards and choose locations it gathers info from. At the moment you either get a Workload view at the Everything level (that loads slow, if at all) and if you want to ignore certain locations you need to use filters to rule out Spaces. Additionally, if you want to use a 1-month Workload you can do that only in individual Spaces. Yes, you can embed a Workload view in a Dashboard card, but that makes for a messy experience where you have another sidebar, another favorites bar, another task tray, and it can be hard to navigate it.

I've been spending some time looking at how teams manage requests and customer inquiries inside project management platforms, and one thing that often comes up is handling data from personal loan lead generation services ( https://pearllemonleads.com/personal-loan-leads/ ) in a more structured way. When lead information arrives from different channels, it can quickly become difficult to track ownership, status changes, and follow-up actions unless there is a clear workflow in place. Having customizable fields, automations, and transparent reporting can make a huge difference for teams that need visibility across the entire process. One feature I'd love to see improved is the ability to build more flexible lead-tracking templates that work right out of the box. Many teams end up creating custom systems from scratch, even though their needs are fairly common. A template that includes stages, follow-up reminders, priority indicators, and activity history would save a lot of setup time and help teams stay consistent when managing incoming opportunities. Another area that could add value is deeper reporting and dashboard customization. It's useful to know not only how many items are entering the workflow, but also where delays occur and which stages create bottlenecks. Being able to visualize conversion trends and response times without relying on external tools would make the platform even more effective for operational teams. Overall, the platform already does a good job of centralizing work, but stronger workflow options for lead-focused processes could make it even more useful. As organizations grow, having a clear and organized way to manage inquiries, assignments, and follow-ups becomes increasingly important, and enhancements in this area would likely benefit a wide range of users.

I need to create a bug-tracking dashboard with multiple sections. Each section should cover one specific problem. Tracking issues across the life cycle within a specific sprint cycle. I want to track all issues in a specific version, including whether they are closed or not. For example, I want to track all issues in version 1, what their status is, all issues in version 2, and what their status is. Status can be: Pending Backlog Done In progress QA Deployed Not deployed Closed I do not want to lose any issues. Quality of the bug tracking. For example, if I create an issue in version 1 and it is in the backlog, and it stays there for a long time while new issues are created, older issues move to ClickUp and it becomes harder to track them. We need to track these issues. Tracking the bugs. This section will track the bugs in order, including which bugs have been created but not fixed, which bugs were created in a later build (e.g., 4 or 5 builds later), and which bugs are duplicates. We need to make sure issues are not too old and that they appear in the dashboard. These are the three dashboard sections I need to create.

Hello! Can I use formula fields too in my Dashboard, in such widgets like Bar chart, etc? Now I only can use money fields, but would really appreciate adding Formula fields too!