Bulk operations

Multi-node actions that apply changes to many nodes at once.

Bulk operations are multi-node actions that apply a change across many nodes at once. They reduce the cost of restructuring large projects or applying consistent updates.

What bulk operations support

Bulk operations include:

  • Status changes: mark multiple nodes complete or reset them to a previous state
  • Type changes: convert several nodes to a different node type
  • Field updates: set a custom field value across multiple nodes
  • Tag application: add or remove tags from a selection
  • Deletion: remove multiple nodes (with confirmation, since removal affects the graph)
  • Move or reparent: change which nodes are prerequisites for the selection

Not all operations are bulk-eligible. Operations that would create cycles or break the graph's acyclic constraint are blocked, the same way they are for single-node edits.

How nodes are selected

Selection works through:

  • Manual click-selection (shift-click or cmd-click for multi-select)
  • Filter-based selection (select all nodes matching a saved filter or query)
  • Tier-based selection (select all nodes in the available tier, or all locked nodes)
  • Branch selection (select all nodes in a specific branch)

Why bulk operations matter

Restructuring a project often means changing many nodes in similar ways. Without bulk operations, each change is a separate action. With bulk operations, the team can restructure quickly while keeping the graph consistent.

Tier availability

Bulk operations are part of the core feature set, available on Free, Paid, and Team.

LAST UPDATED · 2026-05-12