Bug Description
bd update <id> --defer <date> and bd defer <id> --until <date> have inconsistent behavior.
Expected behavior
Both commands should result in the issue showing ❄ (deferred icon) in bd list.
Actual behavior
bd defer jo4g --until=tomorrow → status=deferred ✅ → ❄ shows correctly
bd update jo4g --defer=tomorrow → status=open ❌ → ❄ missing; only the status:deferred label and Deferred: date are set
Steps to reproduce
# Using bd update --defer
bd update stock_brawl2-jo4g --defer=tomorrow
bd list | grep jo4g # Shows ○ (open icon), not ❄
# Using bd defer (correct)
bd defer stock_brawl2-jo4g --until=tomorrow
bd list | grep jo4g # Shows ❄ (deferred icon)
Environment
Additional context
The ❄ icon in bd list appears to be driven by the status field, not the status:deferred label. The --defer flag on bd update sets the label and the Deferred: date metadata, but fails to set status=deferred.
The fix would be for bd update --defer to also set status=deferred to match the behavior of bd defer.
Bug Description
bd update <id> --defer <date>andbd defer <id> --until <date>have inconsistent behavior.Expected behavior
Both commands should result in the issue showing
❄(deferred icon) inbd list.Actual behavior
bd defer jo4g --until=tomorrow→status=deferred✅ →❄shows correctlybd update jo4g --defer=tomorrow→status=open❌ →❄missing; only thestatus:deferredlabel andDeferred:date are setSteps to reproduce
Environment
Additional context
The
❄icon inbd listappears to be driven by thestatusfield, not thestatus:deferredlabel. The--deferflag onbd updatesets the label and theDeferred:date metadata, but fails to setstatus=deferred.The fix would be for
bd update --deferto also setstatus=deferredto match the behavior ofbd defer.