Feature Requests

Please search first before posting to help others find and vote for your idea!
Planning Mode for Workload view — suppress notifications until plan is confirmed (+ revert option)
The Workload view is a powerful tool for resource leveling and smoothing — but rebalancing is inherently iterative. You rarely get the allocation right on the first pass: you move tasks, check capacity, move them again. The issue: every single adjustment (date shift, reassignment) immediately fires a notification to the assignee. By the end of a planning session, team members have dozens of notifications in their Inbox — many of them already outdated, because the plan changed again before they read them. With desktop notifications enabled, the noise is constant. The real damage isn't just the clutter: people learn to ignore ClickUp notifications altogether, which erodes trust in the tool exactly where it matters most. Proposed solution A "Planning Mode" for the Workload view (and potentially Gantt/Timeline): The planner activates Planning Mode and rebalances freely — no notifications are sent while it's active. On "Confirm plan", assignees receive ONE consolidated notification per person summarizing their final changes (e.g. "3 tasks rescheduled, 1 reassigned to you"). A "Discard / revert to original plan" option restores all dates and assignments to their pre-session state. Optionally, exiting the view without confirming prompts: confirm & notify, or discard. Why it matters For mid-size and enterprise teams doing weekly capacity planning across multiple delivery teams, this is the difference between Workload being a true planning tool and a notification cannon. It also aligns naturally with the Workload v2 direction (Work by Day, second-level grouping): the more granular the editing, the more changes per session — and the more urgent batched notifications become. Related: it would also be great to export the Workload view as PDF/PNG, as already possible for Gantt — see also the existing request on exporting utilization percentages.
1
·
Views
Add option to include multi-list ("added") tasks when filtering by list_ids on the Filtered Team Tasks, MCP Tool
Summary: The Filtered Team Tasks endpoint (GET /api/v2/team/{team_id}/task) with the list_ids[] filter only returns tasks whose home List matches. Tasks that have been added to a List via the Tasks in Multiple Lists ClickApp (home List elsewhere) are silently excluded. Please add a parameter to optionally include these location-associated tasks. Current behavior: GET /team/{team_id}/task?list_ids[]={listId} → returns only tasks whose home List is {listId}. A task whose home is List A but is added to List B does not appear when filtering by List B, even though the task object's locations[] array clearly lists B. The per-List endpoint GET /list/{list_id}/task does include explicitly-added tasks, but it can't filter across multiple Lists, statuses, assignees, or date ranges in a single call the way the team endpoint can. Requested behavior: Add a query parameter (e.g. include_lists_tasks=true or match=location) to the Filtered Team Tasks endpoint so that list_ids[] matches a task if any of its locations (home or added) is in the filter — consistent with how the UI shows a task inside every List it belongs to. Use case: We run release automation that pulls every task in a sprint List with a given status (e.g. "Ready for Release" / "In Release") to cross-check against GitLab merge requests. Teams frequently add (not move) a task from a project List into the current sprint List. Those added tasks are invisible to our query, so release-bound work gets silently dropped from the audit. Our only workarounds today are (a) forcing everyone to move instead of add, or (b) querying every possible home List and fetching each task's full detail to inspect locations[] — expensive and brittle. Why the team endpoint specifically: We need the combined filtering (multiple Lists + statuses + assignees + due-date range) that only the Filtered Team Tasks endpoint provides; the single-List endpoint doesn't support those combined filters, so we can't simply switch to it.
0
·
Views
Load More