8000 fix(boardservice): let the planning boards remove work the actor carries by kvaps · Pull Request #316 · aenix-io/aeman · GitHub
[go: up one dir, main page]

Skip to content

fix(boardservice): let the planning boards remove work the actor carries - #316

Merged
kvaps merged 1 commit into
mainfrom
fix/stuck-removals
Nov 9, 2026
Merged

kvaps merged 1 commit into
mainfrom
fix/stuck-removals

Conversation

@kvaps
@kvaps kvaps commented Nov 9, 2026
Copy link
Copy Markdown
Member

A team lead planning their team could not take a task off the Team board, to the backlog or off the board, when somebody else had created it: the server answered 403 notYoursToRemove, the board rolled the optimistic change back, and the card stayed where it was.

The authorship check is meant for a person's own board, where the answer to work planned for you is to refuse it. The Team, Backlog and Strategy boards are where plans are made, and their × now removes such a card. The Me board, view=all and DELETE /cards/{uid} keep the check.

Row S11, docs/api.md, OpenAPI and the MCP remove_card description are updated.

The guard that keeps a person from taking off the board work somebody
else planned for them held on every board. On the Team board, where the
plan is made, it refused a lead every x on a card in their own column
that somebody else had typed: back to the backlog and off the board
alike, so the card stayed on the grid after the optimistic patch rolled
back. The Me board's own refusal sends the person to the board the work
was planned on, which was this one.

The guard now applies to the person's own seat only: DELETE, and the
remove gesture from the Me board or from no board (view=all). The Team,
Backlog and Strategy boards keep the wide x.

Assisted-by: LLM
Signed-off-by: Andrei Kvapil <kvapss@gmail.com>
@kvaps
kvaps merged commit b9d8b46 into main Nov 9, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant

0