Limitations

While projects provide structure and flexibility, there are some constraints to keep in mind:

• Workspace scope → Projects cannot span multiple workspaces. All tasks, stages, and blockers remain local to the workspace they were created in.

• Cross-project dependencies → Direct task dependencies between separate projects are not supported. Dependencies must exist within a single project.

• Ad hoc stages → Stages created on the fly inside a project do not automatically become part of a workflow template; they remain unique to that project.

• Blocker visibility → External blockers (e.g., “waiting for client”) rely on manual updates; Motion cannot detect or clear them automatically.

• Calendar sync → Project tasks sync outward to external calendars for visibility, but edits made externally do not feed back into Motion.

• Bulk editing → While stages and tasks can be moved or reordered, large-scale edits (e.g., renaming multiple stages at once) are limited.

• Archived projects → Once archived, projects are read-only; they cannot be reopened without creating a new project copy.

Key Takeaway Projects are designed to be flexible and structured, but they work best when scoped to one workspace, with dependencies and blockers managed inside that boundary