jira

Track task dependencies and backlog history in Data Visualizer projects by constructing a dependency graph using depends_on, blocks, related_to, and epic_link references. This preserves historical task lists while reflecting real work relationships across epics and bugs.

Suggest the next task to start during sprint planning by applying readiness-based gating. The system evaluates dependency completion, priority, and progress to enforce ready-to-start sequencing and propose the most actionable task.

You can update progress.md and backlog.md without losing previous task records because the system preserves history while applying dependency references. It maintains a historical task list and links related items as progress evolves.

The best way to sequence tasks when blockers prevent starting new work is to map depends_on and blocks relationships across the backlog. This dependency graph identifies blocked items and surfaces ready-to-start tasks that have no unresolved dependencies.

Readiness-based task gating for backlog prioritization works by checking whether all depends_on references for a task are completed. Only tasks with resolved dependencies pass the gate, ensuring sprint planning excludes blocked work and focuses on actionable items.

This task management approach integrates with DV-Orchestrator to prioritize ready-to-start tasks during sprint planning. The orchestrator uses the constructed dependency graph and readiness gating to sequence actionable work automatically.