Skip to main content

Documentation Index

Fetch the complete documentation index at: https://help.statisfy.com/llms.txt

Use this file to discover all available pages before exploring further.

You can drag and drop tasks in the project task grid to change their order or move them into a different parent. This page explains how the drop zones work and what rules apply.

​
Prerequisites

  • An existing project open in the Manage > Projects section
  • The project must be a Statisfy-native project — drag and drop is disabled for projects imported or synced from external sources (e.g., CRM)
  • Clear any active sorts or filters on the task grid if you need to reorder tasks (reparenting still works with sorts/filters active)

​
Drop Zones

When you drag a task over another row, the row is divided into three zones:
ZonePositionAction
Upper thirdTop of the rowInsert the dragged task above this row (reorder)
MiddleCenter of the rowMake the dragged task a child of this task (reparent)
Lower thirdBottom of the rowInsert the dragged task below this row (reorder)
A visual highlight indicates which zone is active as you drag.

​
Reordering Tasks

Drop a task on the upper or lower zone of another task to change its position within the same parent group. The custom order is saved and persists across sessions.
Custom ordering is disabled when a sort or filter is active on the task grid. A toast notification will inform you. In this state, only hierarchy changes (reparenting) are allowed — you must clear the sort or filter to reorder tasks.

​
Reparenting Tasks

Drop a task on the middle zone of another task to make it a child (subtask) of that task. The system validates:
  • Depth limits — The resulting nesting depth cannot exceed the maximum for the root task type (2 levels for regular tasks, 3 for milestones). The full subtree of the dragged task is considered.
  • No circular hierarchy — A task cannot become a child of one of its own descendants.
  • Milestones stay at root — Milestones cannot become subtasks. If you try to drop a milestone into another task, the operation is blocked.
Reparenting a task removes all its existing dependencies — both where it blocks other tasks and where it is blocked. This happens regardless of whether the new parent would violate constraints, so review your dependency chain before moving tasks. See Task Dependencies & Auto-Cascade Dates for details.

Milestones & Task Hierarchy

Understand depth limits and milestone nesting

Task Dependencies & Auto-Cascade

How dependencies and the same-parent constraint work