Skip to content

Metrics

tidanote computes four things automatically. You never fill in a status report — the numbers come from the tasks in your notes.

How much of the project is done.

  • Each task counts: done = 1, doing = 0.5, open = 0.
  • Averaged across the project’s tasks and its sub-projects (recursively).
  • No tasks and no sub-projects → 0%.

Example: two tasks, one done and one doing → (1 + 0.5) / 2 = 75%.

Whether you’re keeping pace with the target date.

  • Compares % complete against % of the time elapsed (from start/created to the target date).
  • Tolerance is ±10%.
  • Only shown when a target date is set and the project isn’t done.

Example: 50% of the time has passed but only 20% is done → Behind.

How fast tasks are being completed.

  • = tasks completed ÷ days, over the last 14 days.

Example: 7 tasks completed in the last 14 days → 0.5 per day.

Whether the project is growing or shrinking — this is the “churn” number.

  • = tasks added − tasks removed, over the last 14 days.
  • Positive = scope grew (creep). Negative = scope was cut.

Example: +3 means three more tasks were added than removed in the last 14 days.

Only appears when a project is past its target date and not done. It names the most likely cause:

  • Slow velocity — few tasks completed.
  • Scope creep — more tasks added than completed.
  • Schedule slip — the target date was too aggressive.

These numbers come from an automatic log of every task change:

  • task_added, task_removed, task_completed, task_reopened
  • due_changed, priority_changed, assignee_changed

Done ≠ removed. Ticking a task is progress; deleting an open task is scope reduction; deleting an already-done task is just cleanup — so it isn’t counted as churn.