Problem
The PATCH /cards/:id endpoint silently ignores parent_card_id in the request body. It returns HTTP 200 but the parent is not updated. This prevents reparenting cards via the API or CLI.
parent_card_id works correctly on POST /cards (create), so the field is supported — just not on update.
Request
- Support
parent_card_id on the PATCH endpoint to allow reparenting cards
- If that won't be supported, return a 4xx error instead of silently ignoring the field — the current 200 response is misleading
Workaround
The --parent-card flag has been removed from suth cards update to avoid confusion. Parent can only be set during creation via suth cards create --parent-card.
Related
Problem
The
PATCH /cards/:idendpoint silently ignoresparent_card_idin the request body. It returns HTTP 200 but the parent is not updated. This prevents reparenting cards via the API or CLI.parent_card_idworks correctly onPOST /cards(create), so the field is supported — just not on update.Request
parent_card_idon the PATCH endpoint to allow reparenting cardsWorkaround
The
--parent-cardflag has been removed fromsuth cards updateto avoid confusion. Parent can only be set during creation viasuth cards create --parent-card.Related