Parent and deps are confusing

[jmmv]

I'm trying to create a "ticket browser" in Emacs that shows a tree of tickets and I just realized something odd....

tk create --parent <id> creates a ticket with a parent field in front matter (a field that doesn't exist by default in other tickets) and does not update the deps field (a field that always shows up as an empty list) of the parent as I was somehow expecting.

This results in dependency tracking "not working":

$ grep qq6n .tickets/*
.tickets/tic-iusr.md:parent: tic-qq6n
.tickets/tic-qq6n.md:id: tic-qq6n
.tickets/tic-zg9c.md:parent: tic-qq6n
$ tk dep tree tic-qq6n
tic-qq6n [open] Epic 3

What's the rationality for the duality between parent and deps? Should parent be eliminated? Or if they serve different purposes, what are those, and could you document those somewhere?

[chinar-amrutkar]

I've created a PR to clarify this. Does it help?

[jmmv]

Thanks, yes, that looks good.

I realized what the difference was for as soon as I started creating a significant number of tasks... but then forgot to come back here.