Update ticket
Change priority, status, category, due date or tags of one ticket.
MCP tool jitbit_write → update_ticket
write Confirm
Updates the fields you pass and leaves the rest. A new ticket must be In process before it can move to a custom status. Moving a ticket to another category runs your automation rules for category changes, and a status change can email the submitter. Tags are added to the ticket, not replaced. By default you confirm each call; you can switch that off for this tool.
Parameters
| Name | Type | Description |
|---|---|---|
| ticket_id integer required | integer | Ticket ID from list_tickets or search_tickets. |
| priority string | string | Priority name: Low, Normal, High, Critical or a custom one. |
| status string | string | Status name from your helpdesk, for example In process or a custom status. |
| category_id integer | integer | Category ID from list_categories. |
| due_date string | string | ISO date. |
| add_tags string[] | string[] | Tags to add, keeping the existing ones. |
tools/call
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "jitbit_write",
"arguments": {
"operation": "update_ticket",
"arguments": {
"ticket_id": 1
}
}
}
}Example response
{
"content": [
{
"type": "text",
"text": "{ ... same JSON as structuredContent ... }"
}
],
"structuredContent": {
"ticket_id": 5128,
"status": "In process",
"priority": "High",
"category": "Technical support",
"due_date": null,
"tags": [
"login"
],
"updated_at": "2026-10-22T09:02:00Z"
},
"isError": false
}