Executive Summary While ClickUp allows assigning multiple users to a single task, the entire task is restricted to a single global Start and Due Date. Grouping views by assignee does not solve task-level timeline allocation. We urgently need individual, per-assignee Start and Due Date ranges within a single task container to accurately model sequential handoffs, overlapping reviews, and workload scheduling without cluttering lists with redundant subtasks. The Problem & Operational Friction Currently, when 2+ team members are assigned to one task: Workload Misrepresentation: Assignee B appears "active" on day 1 on Workload/Calendar views, even if their contribution doesn't start until day 5 after Assignee A finishes their part. Subtask & Task Bloat: Teams are forced to create 3–5 artificial subtasks (e.g., "Design", "Dev", "QA") just to assign separate dates, creating massive hierarchy clutter. Communication Overhead: Team members must constantly ping each other in comment threads to clarify, "When is my part actually due?" Proposed Solution Allow each assigned user on a multi-assignee task to have their own dedicated Start Date and Due Date fields tied to their profile icon. Real-World Use Cases Scenario A: Sequential Handoff (Linear Dependency) Task: Feature Specification & Engineering Hand-off Assignee A: Start: July 20, 2026 | Due: July 24, 2026 Assignee B: Start: July 25, 2026 | Due: July 28, 2026 Impact: Assignee B’s Workload View only reflects activity starting July 25th. No manual check-in needed. Scenario B: Staggered / Overlapping Collaboration Task: Cross-Functional Audit & Compliance Package Assignee A: Start: July 20, 2026 | Due: July 24, 2026 Assignee B: Start: July 22, 2026 | Due: July 30, 2026 (Overlaps Assignee A by 2 days for various reasons) Assignee C: Start: July 23, 2026 | Due: July 29, 2026 (Parallel execution track) Impact: All 3 collaborators have distinct, transparent windows of accountability directly visible on their personal calendars. Business Impact & Value for ClickUp Drastic Reduction in Task Bloat: Eliminates thousands of unnecessary micro-subtasks created solely for date-tracking purposes. True Workload View Accuracy: Empowers resource managers to see actual capacity based on when an individual is actually scheduled to work on a task, not just when the global task is open. High Community Demand: Solves a major pain point for cross-functional game studios, agency teams, and enterprise product organizations managing tight release pipelines.