Cycles as releases: web UI to create/close, and archive done issues on close #37

Closed
opened 2026-09-05 10:44:55 +08:00 by Breadway · 0 comments
Owner

User: "having a different board for different releases may be good... after [BOS 0.6.2] is shipped it'd be nice to be able to archive the DONE column."

Breadboard already has a Cycle concept (name, starts_on, ends_on, closed) that's cross-project and has full backend/CLI support, but no web UI at all — no way to create one, assign an issue to one, or close one from the browser. Building on that instead of a new "release" concept:

  • Settings gets a Cycles section: list with issue counts, new-cycle form, close/reopen action.
  • IssueDrawer gets a Cycle selector (currently missing entirely).
  • store.filtered excludes done issues belonging to a closed cycle from the default board/backlog view (only when no cycle filter is active) — "archived", not deleted; still fully visible by selecting that cycle from the existing header dropdown.
User: "having a different board for different releases may be good... after [BOS 0.6.2] is shipped it'd be nice to be able to archive the DONE column." Breadboard already has a Cycle concept (name, starts_on, ends_on, closed) that's cross-project and has full backend/CLI support, but no web UI at all — no way to create one, assign an issue to one, or close one from the browser. Building on that instead of a new "release" concept: - Settings gets a Cycles section: list with issue counts, new-cycle form, close/reopen action. - IssueDrawer gets a Cycle selector (currently missing entirely). - store.filtered excludes done issues belonging to a *closed* cycle from the default board/backlog view (only when no cycle filter is active) — "archived", not deleted; still fully visible by selecting that cycle from the existing header dropdown.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
Breadway/breadboard#37
No description provided.