move_task
Relocate a task to a different project, carrying over labels, assignees, comments, relations, and dates. Requires write access to the destination project.
Instructions
Move a task to another project. Needs write access to the target.
Vikunja has no endpoint for this. A task's project_id is writable and setting
it is the move. This costs what an update costs: two requests on v1, one on v2.
Labels, assignees, comments, relations, and dates all come along. The
project-local identifier derives from the project the task is in, and is
reassigned on arrival.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"task_id": "<task_id>",
"project_id": "<project_id>"
},
"name": "move_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| task_id | Yes | ||
| project_id | Yes |