Set due dates by task name (from parent date)
TL;DR: Use this when you have 3–6 standardized task names (e.g. "Design", "QA", "Review") and each name should have its own fixed offset from the parent item's date. Set up one automation per task name. Each takes ~3 minutes.
What this does
When a subitem is created with a specific name, this automation sets its date to the parent item's date plus a fixed offset. Different names get different offsets — for example:
- "Design" → Parent date + 3 days
- "QA" → Parent date + 14 days
- "Review" → Parent date + 21 days
When to use it
Best fit:
- You have standardized task names across projects
- 3–6 task types total
- Each task name needs its own consistent offset
If task names vary widely or you have many task types, use Set per-task due dates using a Numbers column instead — it scales without needing one automation per task.
Before you start
- A Date column on the parent item (the reference date) and a Date column on the subitem (the date to set)
- A list of standardized task names you want to automate, with the offset for each
Set up your first task type
Open the Automations Center on your board (Automate → Create).
Copy this recipe text and find it in your board's automation center: "When subitem is created and if the name is this name, set due date to match parent item due date + X days/weeks." Click Use Template.
Configure the underlined fields:
is this name
The exact name of the subitem this rule applies to
Design
subitem date
The date column on the subitem to set
Due Date
parent item date
The reference date on the parent item
Project Start
+ X Days/Weeks/Months
Direction (+ or −), amount, and unit
+3 Days
Example end state:
When subitem is created and if name is "Design"→ set Due Date to Project Start + 3 Days
Click Create automation.
Repeat for each task type
Create one automation per task name. Example:
Design
+3 days
Development
+7 days
QA
+14 days
Review
+21 days
Test that it works
Create a subitem named exactly "Design" under an item that has a Project Start date.
Confirm the subitem's Due Date = Project Start + 3 days.
Repeat for each task name to confirm each automation fires correctly.
Common gotchas
- Names are case-sensitive and exact. "Design" ≠ "design" ≠ "Design " (trailing space).
- One automation per task name. If you add a new task name later, you need to add a new automation for it.
- Use negative numbers for dates BEFORE the parent date. e.g. event planning: "Venue Booking" = Event Date −90 days.
- Date columns must exist on both the parent and the subitem. The columns don't need the same name, but they must exist.
Next up
Related
- Date & timeline automations (parent landing)
- Date + offset — full reference (the comprehensive date+offset guide)
- Set due dates by task name (from creation) (creation-date variant)
Still stuck?