Repository navigation
Conversation
…726) **Why** A user with many tasks to move from one project to another can ask the AI (EVA or Claude, through the MCP tools) to do it; no MCP tool moved a task to another project (EXO-93025). **How** - New MCP tool `move_tasks_to_project` (`TaskMcpTool#moveTasksToProject`, `ai-tool-definitions.json`): up to 100 task ids, a target project and an optional status of that project, its default status otherwise; `require_approval`, declared destructive like `update_task_status`. - The tool checks first: the target project's view permission, every task's edit permission, the status belonging to the target project. A target project without statuses gets its initial ones, only after those checks. - `TaskService#moveTasks` writes the move in one `@ContainerTransactional(atomic = true)` transaction: a task refused midway rolls the earlier writes back, nothing is moved. The update events are broadcast after it returns, so after the commit on the MCP path, which opens no transaction of its own. - `TaskServiceImpl#updateTask(long, TaskDto, Identity)` is split into `authorizeUpdate`, `persistUpdate` and `broadcastUpdate`, so the bulk move reuses the single-task move's authorization as is. - The tasks keep their labels, as a move from the task drawer does. - Tests: `TaskMcpToolTest` (the tool's checks and their order, the definition's hints), `TaskServiceMoveTasksTest` (real container and database: all moved and events after the commit; refused midway, none moved and no event). Knowledge: Meeds-io/eng-standards#1213, #1214, #1215, #1231 This change is classified N1 (computed at b089b07): its approver must be an Archi/Dev who knows it is N1, not an approval on AI review alone; author ≠ approver. 🤖 Generated with [Claude Code](https://claude.com/claude-code) --------- Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com> (cherry picked from commit dd2b4bb)
|
Source: #726, Picks:
Adaptations: none. The pick applied clean and no commit was added. Verification:
Level: N1, restated from #726 (new MCP tool definition; ACL checks in |
|



Why
A user with many tasks to move from one project to another can ask the AI (EVA or Claude, through the MCP tools) to do it; no MCP tool moved a task to another project (EXO-93025).
How
move_tasks_to_project(TaskMcpTool#moveTasksToProject,ai-tool-definitions.json): up to 100 task ids, a target project and an optional status of that project, its default status otherwise;require_approval, declared destructive likeupdate_task_status.TaskService#moveTaskswrites the move in one@ContainerTransactional(atomic = true)transaction: a task refused midway rolls the earlier writes back, nothing is moved. The update events are broadcast after it returns, so after the commit on the MCP path, which opens no transaction of its own.TaskServiceImpl#updateTask(long, TaskDto, Identity)is split intoauthorizeUpdate,persistUpdateandbroadcastUpdate, so the bulk move reuses the single-task move's authorization as is.TaskMcpToolTest(the tool's checks and their order, the definition's hints),TaskServiceMoveTasksTest(real container and database: all moved and events after the commit; refused midway, none moved and no event).Knowledge: Meeds-io/eng-standards#1213, #1214, #1215, #1231
This change is classified N1 (computed at b089b07): its approver must be an Archi/Dev who knows it is N1, not an approval on AI review alone; author ≠ approver.
🤖 Generated with Claude Code