Dependencies

Dependencies declare execution order: one task or event must finish before the next one can begin. Mitra visualizes these connections directly on your calendar grid and alerts you whenever a schedule conflict arises.

Creating a dependency

In any entry’s editor under Relations:

1. Select ＋ Relation.
2. Choose Blocks (if this entry must happen before the target) or Depends on (if this entry requires the target to finish first).
3. Search for the prerequisite or follow-up entry.

Mitra records the relationship from both sides — adding “A blocks B” automatically shows “B depends on A” on entry B.

Visual connection arrows

On the calendar grid (Day and Week views), Mitra draws smooth connection arrows between dependent entries:

• The line starts at the end of the prerequisite entry and points to the start of the dependent entry.
• Clicking or hovering over an entry highlights its active dependency lines so you can trace complex workflows at a glance.

Schedule conflict warnings

If an entry is moved or scheduled such that it starts before its prerequisite has finished, Mitra flags a dependency violation:

• The connecting arrow changes color to indicate a conflict.
• The entry displays a warning badge, making it easy to spot scheduling mistakes on your timeline.
• Moving the dependent task back after the prerequisite resolves the warning automatically.

Moving dependent entries

When you move or reschedule an entry that has dependent tasks or events linked to it, Mitra offers smart options to keep your schedule organized:

• Only this entry: Moves only the selected entry and leaves all related entries at their current times.
• Keep the chain intact: Shifts follow-up entries forward just enough to avoid schedule conflicts. If an entry already has enough buffer time before it begins, it stays right where it is.
• Move them all by the same amount: Shifts all connected entries in the chain by the exact same amount of time, preserving the time gaps between your tasks.

TIP

Hold Ctrl (or ⌘ on macOS — see keyboard shortcuts) while dragging an entry to bypass the prompt and move only the selected entry.

Subtasks and recurring events

• Subtasks move along: When a task moves as part of a dependent chain, its subtasks move along with it so child tasks stay within their parent project’s timeframe.
• Recurring and unscheduled tasks: Recurring event series and unscheduled tasks in a dependency chain are not moved automatically, preventing unexpected changes to repeating rules or task lists.

See also

• Relationships Overview →
• Hierarchy →
• Keyboard Shortcuts →