ClickUp Gantt: Auto-Schedule Parent Tasks & Skip Weekends

ClickUp Rebuilt the Gantt Engine

Most of this week’s news traces back to one foundational change: ClickUp rebuilt the engine that drives Gantt scheduling. Instead of separate logic in different places, one shared engine now handles how date changes propagate across durations, dependencies, parent-child relationships, and non-working days.

It’s infrastructure work, so there’s no flashy changelog card. But it’s the foundation that unlocks the two features below, and the ones still coming.

Parent Task Dates Auto-Remap From Subtasks

Turn this on and parent dates stop drifting out of sync. The parent’s start date matches the earliest subtask start, the due date matches the latest subtask due, and both update automatically as subtasks move.

A few details worth knowing:

• Enable it per list - right-click a list or open List Settings
• Works across views - Gantt, List, and Task views all respect it
• Stays editable - if a subtask falls outside the parent’s range, ClickUp prompts you to sync in one click, and parent dates remain editable with a quick confirm

Skip Non-Working Days

Set a task’s duration and ClickUp schedules around weekends and your configured non-working days automatically. The key word is consistently: it holds across reschedules, subtask remaps, and automations, so your timeline doesn’t quietly drift onto a Saturday. Non-working days render grey in week view.

Rewind: Forms

A quick revisit of ClickUp Forms - still one of the most underused ways to standardize intake and route work to the right place automatically.

On the Wish List

Different statuses for tasks and subtasks. Today subtasks inherit the parent’s full status pipeline. The request: let subtasks run a simpler status set of their own, so a quick checklist item isn’t forced through the same stages as a major deliverable.

In the Wild

Three patterns worth stealing from real workspaces:

• Auto-set due dates from a start date. A People & Culture team rebuilt their onboarding template so every task’s due date sets automatically relative to each new hire’s start date, with reminders firing a couple days ahead.
• A dedicated Operations space. A team carved out a separate Operations space (not just a folder) for internal, non-project work like meetings, admin, and PTO, so project reports and resourcing data stay clean.
• Don’t merge custom fields. Merging two custom fields generates a new backend field ID, which silently breaks any automation or agent pointing at the old one. Deprecate unused fields and redirect teams to the survivor instead.