Verify bulk_move_items backend supports points field #34

New issue

Closed

opened 2026-03-13 06:54:39 +00:00 by forgejo_admin · 0 comments

forgejo_admin commented

2026-03-13 06:54:39 +00:00

Owner

Lineage

todo-mcp-clear-points-labels (no plan ancestry — discovered during PR #32 QA)

Repo

forgejo_admin/pal-e-docs-mcp + forgejo_admin/pal-e-docs (backend verification)

User Story

As a sprint manager using bulk_move_items
I want confidence that passing points in the JSON array actually works
So that bulk operations don't silently drop data

Context

PR #32 updated bulk_move_items documentation to advertise points as a valid key in the JSON array. QA nit #2: The MCP tool passes the parsed JSON list directly to the SDK, which passes it to the API. If the backend bulk endpoint doesn't support points in its schema, callers get a silent drop or validation error.

This is a verification task — confirm the backend PUT /api/sprints/{slug}/items/bulk accepts points per item, and if not, either fix the backend or correct the MCP documentation.

File Targets

Files to verify:

pal-e-docs/src/pal_e_docs/routes/sprints.py — bulk endpoint schema
pal-e-docs-sdk/src/pal_e_docs_sdk/sprints.py — SDK bulk method
src/pal_e_docs_mcp/tools/sprints.py — bulk_move_items docstring (line ~309)

Acceptance Criteria

Verified: backend bulk endpoint either accepts points per item OR documentation is corrected
If backend doesn't support it: either add support OR remove points from bulk_move_items description
No silent data drops — behavior matches documentation

Test Expectations

Manual test: bulk_move_items with points in JSON payload — verify points actually saved
If fix needed: ruff check and ruff format --check pass

Constraints

May touch pal-e-docs backend if the fix is there (coordinate with pal-e-docs repo)
Prefer fixing the backend over removing MCP documentation — points in bulk is useful

Checklist

Verification complete
PR opened (if code change needed)
Tests pass
No unrelated changes

pal-e-sprints — project
PR #32 — QA nit #2

### Lineage `todo-mcp-clear-points-labels` (no plan ancestry — discovered during PR #32 QA) ### Repo `forgejo_admin/pal-e-docs-mcp` + `forgejo_admin/pal-e-docs` (backend verification) ### User Story As a sprint manager using bulk_move_items I want confidence that passing `points` in the JSON array actually works So that bulk operations don't silently drop data ### Context PR #32 updated `bulk_move_items` documentation to advertise `points` as a valid key in the JSON array. QA nit #2: The MCP tool passes the parsed JSON list directly to the SDK, which passes it to the API. If the backend bulk endpoint doesn't support `points` in its schema, callers get a silent drop or validation error. This is a verification task — confirm the backend `PUT /api/sprints/{slug}/items/bulk` accepts `points` per item, and if not, either fix the backend or correct the MCP documentation. ### File Targets Files to verify: - `pal-e-docs/src/pal_e_docs/routes/sprints.py` — bulk endpoint schema - `pal-e-docs-sdk/src/pal_e_docs_sdk/sprints.py` — SDK bulk method - `src/pal_e_docs_mcp/tools/sprints.py` — `bulk_move_items` docstring (line ~309) ### Acceptance Criteria - [ ] Verified: backend bulk endpoint either accepts `points` per item OR documentation is corrected - [ ] If backend doesn't support it: either add support OR remove `points` from `bulk_move_items` description - [ ] No silent data drops — behavior matches documentation ### Test Expectations - [ ] Manual test: `bulk_move_items` with `points` in JSON payload — verify points actually saved - [ ] If fix needed: `ruff check` and `ruff format --check` pass ### Constraints - May touch pal-e-docs backend if the fix is there (coordinate with pal-e-docs repo) - Prefer fixing the backend over removing MCP documentation — points in bulk is useful ### Checklist - [ ] Verification complete - [ ] PR opened (if code change needed) - [ ] Tests pass - [ ] No unrelated changes ### Related - `pal-e-sprints` — project - PR #32 — QA nit #2