Set due dates by task name (from creation)

Set due dates by task name (from creation)

TL;DR: When a subitem is created with a specific name, set its date to today + a fixed offset for that name. Like "Set due dates relative to creation" but selective — fires only when the subitem name matches. One automation per task type.

What this does

For subitems with a specific name (e.g. "Triage", "First response", "Resolution"), set the date to creation date + a per-name offset. Different names get different offsets.
Example: SLA-style support workflow — Triage due in 1 day, First response in 5 days, Resolution in 14 days.

When to use it

  • SLA workflows where different task types need different timings
  • Standardized task names (3–6 distinct names)
  • Each task name should get a fixed, consistent offset every time
If every subitem should get the same offset regardless of name, use  Set due dates relative to creation⁠  instead.

Before you start

  • 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 Automate → Create on your board.
    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 creation date + X days/weeks." Click Use Template.
    Configure the underlined fields:
Field
What to select
Example
is this name
The exact name of the subitem this rule applies to
Triage
due date
The date column on the subitem to set
Due Date
+ X days/weeks/months
Direction (+ or −), amount, and unit
+1 Day
    Click Create automation.

Repeat for each task type

Create one automation per task name. Example for a support workflow:
Task name
Offset from creation
Triage
+1 day
First response
+5 days
Resolution
+14 days

Test that it works

    Create a subitem named exactly "Triage".
    Confirm its Due Date = today + 1 day.
    Repeat for each task name to confirm each automation fires correctly.

Common gotchas

  • Names are case-sensitive and exact. "Triage" ≠ "triage" ≠ "Triage " (trailing space).
  • One automation per task name. Add a new task name later → add a new automation for it.
  • Subitems with non-matching names get no date set — by design. If you want a fallback for unmatched names, also add the blanket  Set due dates relative to creation⁠  variant.
  • Date column must exist on the subitem.

Next up

Related

  •  Date & timeline automations⁠  (parent landing)
  •  Set due dates by task name (from parent date)⁠  (same logic but offset from parent date, not creation date)

Still stuck?

Email  hello@fantasymedia.io  and we'll help you configure the right SLA timing for each task type.