Feature Request
When archiving a parent card, its children are left behind as orphans. A --cascade flag would archive the parent and all its children in one operation.
Proposed usage
# Archive parent and all children
suth cards update 390 --archived --cascade -y
# Current behavior (without --cascade): only archives card 390, children remain
Context
During triage of the Infrastructure pipeline, we archived tracker card 390 (FT046 CI/CD & Deployment Automation) but its child card 403 (Auto-deploy DevDocs) was left behind on Sprint 12. The child had to be archived separately — and couldn't be, due to #71.
Implementation notes
- Fetch the card's
child_cards array
- Archive each child, then the parent
- Could also be useful for
--cascade on other operations (move, tag, etc.) but archiving is the immediate need
Feature Request
When archiving a parent card, its children are left behind as orphans. A
--cascadeflag would archive the parent and all its children in one operation.Proposed usage
Context
During triage of the Infrastructure pipeline, we archived tracker card 390 (FT046 CI/CD & Deployment Automation) but its child card 403 (Auto-deploy DevDocs) was left behind on Sprint 12. The child had to be archived separately — and couldn't be, due to #71.
Implementation notes
child_cardsarray--cascadeon other operations (move, tag, etc.) but archiving is the immediate need