Convert 31 deprecated todo-type board items to Forgejo issues #205
Labels
No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
forgejo_admin/pal-e-api#205
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Type
Feature
Lineage
Standalone — board-pal-e-agency board hygiene
Repo
forgejo_admin/pal-e-docs(API for board operations)User Story
As the superuser
I want deprecated todo-type board items converted to proper Forgejo issues
So that every board item has a real scope document and the deprecated item_type is eliminated
Context
31 board items across all boards use
item_type="todo"which is deprecated. These referencetodo-*notes instead of Forgejo issues. Perfeedback_no_todo_notes, work items should be Forgejo issues. This ticket converts each todo item: create a Forgejo issue from the todo note content, update the board item toitem_type="issue"with the newforgejo_issue_url, then archive the todo note.What Broke
Not a bug — cleanup of deprecated pattern. The
todoitem_type predates the kanban-over-plans convention.File Targets
Board operations via MCP:
Acceptance Criteria
Test Expectations
list_board_items(board_slug="board-pal-e-platform", item_type="todo")returns emptyConstraints
Checklist
Related
feedback_no_todo_notes— the policyconvention-kanban-over-plans— the philosophyTodo-to-Issue Migration Complete
Summary
Converted all deprecated todo-type board items to Forgejo issues across all active boards. Zero todo-type items remain.
Done Items Removed (16 total)
Removed from boards and archived the underlying notes:
Active Items Converted (10 total)
Each todo was: read -> Forgejo issue created -> old board item removed -> new issue-type board item created (preserving column, position, points) -> todo note archived.
Items Removed Without Conversion (1)
Verification
All 13 boards queried with
item_type="todo"-- all return empty arrays.All acceptance criteria met:
Closing.
Todo-to-Issue Conversion Complete
Converted all 4 remaining
item_type="todo"board items toitem_type="issue"with proper Forgejo issues.Conversions
remember-landing-page-frontend-soppost-gratitude-psychology-degreepost-what-is-a-platformpost-hallucinations-corporate-problemVerification
todoitems initem_countsitem_type="issue"withforgejo_issue_urlsettype:featureand appropriatearch:componentNote
The issue mentioned 31 todo items, but most had already been converted. Only 4 remained across 2 boards (board-remember: 1, board-posts: 3).