Project not found.

Phase: Sprint Schema Expansion (repo/project boards + needs_approval)

phase-sprints-schema-expansion Phase

Goal: Expand sprint schema for five boards, human review gate, and item estimation.
Owner: Dev agent
Repo: forgejo_admin/pal-e-docs + forgejo_admin/pal-e-docs-mcp

Scope

  • repo/project item_types + needs_approval column — PR #67 merged (squash). Forgejo issue #66 (closed). DONE.
  • Points field on sprint items — PR #69 merged (squash). Nullable integer points on SprintItem. Forgejo issue #68 (closed). DONE.
  • MCP tool updates — PR #32 merged (squash, pal-e-docs-mcp). Forgejo issue #11 (closed). DONE. QA nits tracked as #33 and #34.

Decisions

Decision Rationale
Points on items only, not plans/phases Plans are containers, phases are organizational. Items (issues) are the unit of work. Velocity = sum of pointed items completed per sprint.
Points field is optional (nullable integer) Not all items need points. Unpointed items are valid (e.g. backlog items not yet estimated).
Fibonacci scale (1/2/3/5/8) Standard estimation scale. Calibrate as we go.
Separate PR for points (Option B) PR #67 was already scoped. Don't add scope to unreviewed PRs.
Sprints = committed scope, not timebox A sprint is a set of well-scoped items we commit to. Not a fixed timeline. Keep pushing until done, then close.

Status

  • PR #67 (repo/project + needs_approval): MERGED. Issue #66 closed.
  • PR #69 (points field): MERGED. Issue #68 closed.
  • PR #32 (MCP tools update, pal-e-docs-mcp): MERGED. Issue #11 closed. QA nits: #33 (clear points/labels), #34 (verify bulk points).
Depends on: Phase 1 (tables + API) — COMPLETED