-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Description
Bug: bd dep tree does not traverse 'blocks'-type dependency edges
Version
bd version 0.55.4
Description
bd dep tree <issue-id> always shows the root issue as [READY] with no children, even when bd dep list <issue-id> correctly shows blockers. The issue appears to be that dep tree does not traverse dependency edges stored as blocks relationships.
Steps to Reproduce
Given an issue with blockers (e.g. bd show reports it as blocked):
$ bd dep list myproject-abc
π myproject-abc depends on:
myproject-x: Some blocker task [P2] (open) via blocks
myproject-y: Another blocker [P2] (open) via blocks
$ bd dep tree myproject-abc
π² Dependency tree for myproject-abc:
myproject-abc: My Epic [P1] (open) [READY]
The tree shows no children despite the issue having blockers. Passing --type blocks explicitly makes no difference.
Root Cause (suspected)
dep list shows the relationships are stored as "via blocks" edges. It appears dep tree --direction=down traverses depends_on edges rather than blocks edges, so it finds nothing. bd graph <issue-id> works correctly for the same issue, suggesting it uses a more complete traversal.
Expected Behaviour
bd dep tree myproject-abc should show the same blockers that bd dep list myproject-abc shows, laid out as a tree.
Workaround
Use bd graph <issue-id> --compact instead β it correctly shows the full dependency structure.