Main Use Cases
Everything you need to know about setting up your multi-level automations and understanding their basic behaviour & logic.
Sync Values Between Parent Item & Subitem:
Keeping values consistent across all 5 levels of your multi-level board is where great workflows live and bad ones die. With Multi-Level Subitem Automations, one change at the top cascades cleanly through every subitem.
Use Cases:
- Project kickoffs that trigger status updates across every level
- Priority changes that propagate from parent items down to every subtask
- Ownership reassignments that flow automatically through the hierarchy
So, what kind of automations can you create?
- When a column changes on an item, sync that new value to every subitem in one call — dates, statuses, owners, priorities, all synced top-down
- Maintain alignment across deep hierarchies without clicking through each level manually
Set Default Values on Creation: Start Right, Every Time
Why start every new subitem from scratch? Setting defaults at creation gives your team a head start and keeps every new subitem consistent with its parent — no forgotten fields, no manual setup.
Use Cases:
- Inherit owner, status, dates, or priority from the parent item
- Apply naming conventions that prefix or suffix the parent's name
- Enforce consistent structure across multi-level boards
So, what kind of automations can you create?
- When a subitem is created, automatically copy a parent column value onto it — any column type, from status to dates to dropdowns
- Auto-prefix or suffix the parent's name to every new subitem with a custom connector, keeping nested work readable in every list, export, and dashboard
Copy Subitem Structures: Replicate Multi-Level Workflows in Seconds
Building the same multi-level subitem tree every new project wastes hours. Turning an existing subitem structure into a reusable template means your team replicates proven workflows in seconds, not hours.
Use Cases:
- Launching new client projects with the same task breakdown
- Recreating standard sprint structures across teams
- Copying approval workflows between departments or boards
So, what kind of automations can you create?
- When a new item is created, copy all subitems from a chosen source item — with column values mapped across boards by name and type
- When an item or subitem's status changes to something, trigger the same copy automatically — so templates deploy based on project milestones
Convert Subitems to Items: When a Subitem Grows Into Its Own Project
Sometimes a subitem grows into something bigger — a task becomes a full project, or an idea becomes its own workstream. Instead of manually rebuilding it, promote it instantly into a top-level item on any board.
Use Cases:
- A sales opportunity subitem becomes its own deal on the Pipeline board
- A feature idea subitem becomes a standalone development project
- An internal ticket subitem becomes a full client engagement
So, what kind of automations can you create?
- When a subitem's status changes to something, automatically convert it to a standalone item on any board — column values mapped during the move
Putting It All Together
Considering these five strategies when building your work processes will simplify your day-to-day work.. By implementing them thoughtfully, you'll transform your workflows into a well-oiled machine where subitems and parent items coexist in perfect harmony.
Remember, automation isn't about replacing human insight—it's about freeing up your team's time for more strategic thinking. After all, the best project managers aren't the ones doing all the work; they're the ones who know how to make the work flow smoothly and efficiently.
Let's Continue, Security & Privacy→