Let issues move through Ideas, Design, and Build stages

arne commented

2026-04-05 13:11:46 +02:00

Owner

Every open issue currently lands in the Ideas stage of the project detail page because orbit has no way to record which stage an issue belongs in. The design system spec laid out a flow — Ideas, Design, Build, Review, History — and ideas already carry a status field that distinguishes raw, developing, and ready. Issues need an equivalent so they can graduate from Ideas to Design to Build as work progresses.

Three directions worth brainstorming before any implementation:

A stage column on the issues table (ideas | design | build), set manually via an MCP tool or derived from Forgejo labels.
Label-based convention: a Forgejo label like stage:design moves an issue to the Design stage automatically on sync. Keeps the state in Forgejo rather than orbit's store.
Leave it alone — at orbit's tiny scale, ideas with status developing/ready may carry the flow well enough, and issues staying in Ideas may be fine in practice.

Decide during a brainstorming session before implementing.

Scope

In bounds: the mechanism for moving an issue between stages and the corresponding display logic in the project handler. Out of bounds: any UI changes beyond the stage assignment, and the owner-prefix fix from the related open issue — that's orthogonal.

Every open issue currently lands in the Ideas stage of the project detail page because orbit has no way to record which stage an issue belongs in. The design system spec laid out a flow — Ideas, Design, Build, Review, History — and ideas already carry a `status` field that distinguishes `raw`, `developing`, and `ready`. Issues need an equivalent so they can graduate from Ideas to Design to Build as work progresses. Three directions worth brainstorming before any implementation: - A `stage` column on the `issues` table (`ideas` | `design` | `build`), set manually via an MCP tool or derived from Forgejo labels. - Label-based convention: a Forgejo label like `stage:design` moves an issue to the Design stage automatically on sync. Keeps the state in Forgejo rather than orbit's store. - Leave it alone — at orbit's tiny scale, ideas with status `developing`/`ready` may carry the flow well enough, and issues staying in Ideas may be fine in practice. Decide during a brainstorming session before implementing. ## Scope In bounds: the mechanism for moving an issue between stages and the corresponding display logic in the project handler. Out of bounds: any UI changes beyond the stage assignment, and the owner-prefix fix from the related open issue — that's orthogonal.

arne changed title from ~~project-detail: per-issue triage between Ideas/Design/Build stages~~ to Let issues move through Ideas, Design, and Build stages

2026-04-05 22:34:00 +02:00

arne closed this issue

2026-04-06 18:34:22 +02:00

Rows
Columns

Let issues move through Ideas, Design, and Build stages #9

Scope