TodoPro

Config-driven hierarchical todo / ticket manager as a VS Code extension.

Data files (per workspace)

TodoPro is project-scoped. Runtime data lives under the opened folder:

<workspace-root>/
  todopro/
    config.xml
    tickets.xml
    backups/

On first open, if those files are missing, TodoPro asks whether to Generate default TodoPro files (copies from extension-bundled templates). Cancel leaves the project untouched.

Templates (extension package only — not runtime SSOT):

• extension/data/config.example.xml
• extension/data/tickets.example.xml

Git tip: commit todopro/config.xml and todopro/tickets.xml so the team shares board state. Add todopro/backups/ to .gitignore if you do not want local backups in the repo.

Multi-root workspaces use the first workspace folder only (v1).

Develop

cd extension
npm install
npm run build

Then press F5 (launch config: Run TodoPro Extension), or run command TodoPro: Open.

Commands

• TodoPro: Open — Application panel
• TodoPro: Open Settings — Settings panel
• TodoPro: Restore Backup — pick a backup and restore into workspace todopro/

Core behavior

• Hierarchy via ParentTicketKey / EpicKey
• Dependencies via LinkedTickets + config Relationships (Depends on / Blocked by)
• Summary bars over each top-level ticket under the selected Epic
• Safe / cascade delete, autosave XML writes (no automatic backup copies)
• Manual backup from Settings → Create backup into todopro/backups/
• Globally unique uniqueid values across config + tickets