v1.56.0
Highlights
- Task filenames follow title edits. Renaming a task keeps its ID and its links. When an ID has different filenames across branches, Backlog uses the creation time to the second to recognize the same task. Scripts that store a Markdown path should update it after a rename. (#1229)
- Create, edit, and read decisions from the CLI. Use
--context, --decision, --alternatives, and --consequences to write individual sections. Use --superseded-by to link a replacement decision. backlog decision view <id> reads active or archived decisions and supports --json. (#1165, #1166)
- Custom workflows use their final column consistently. Project statistics, milestone progress, and board completion marks follow the last configured status, including when an earlier column is named Done. (#1226, #1227)
Markdown files
- Tasks, drafts, documents, and decisions save creation and update times in UTC to the second, for example
2026-11-21T09:30:45Z. Editing a record with a standard --- header converts older timed values. Date-only values stay date-only. (#1229)
- Markdown metadata must use YAML. When writing records by hand, place the YAML fields between two
--- lines.
Fixes
- Switching branches with a large terminal board open uses less memory. Long documents scroll with the keyboard and mouse wheel. (#1223, #1222)
- The browser keeps unsaved task and draft edits visible when the file changes elsewhere and asks for a refresh before saving. Archiving a draft from the browser preserves any existing archive file. (#1215, #1213)
- Saving settings preserves custom YAML keys and comments. (#1214)
- Board export writes to the absolute path you supply. Thanks to @batou9150. (#1219)
- Cross-branch task views respect the configured status order when choosing the most progressed version. Compact JSON task lists and search results include direct dependencies. CLI output exits cleanly when a pipe reader stops early. (#1168, #1153, #1190)
Full changelog from v1.55.3 to v1.56.0