KAN-72 lets agents refine existing tickets entirely through MCP: update_ticket edits all supported ticket fields and the real acceptance checklist, get_ticket accepts an exact ticket key, and paginated search/project discovery plus compact current workflow configuration provide the required IDs without scanning status lists.
Updates reuse the existing UI validation, transactional action, worklog and notification behavior. Omitted fields remain unchanged, nullable scalar null clears values, and supplied checklist/custom-field lists replace the list ([] clears it). Existing checklist IDs remain stable; new entries get new IDs, and foreign/duplicate IDs are rejected. Workflow changes continue through move_ticket_status. Existing tools remain compatible.
Validation: affected MCP, project-ticket controller and API tests pass; frontend build and PHP formatting pass. Regression coverage includes application-key HTTP refinement, permission-scoped pagination, parent/author/person rules, checklist identity and rollback. The PR targets its recorded base main (ba12e65).
Production acceptance is still pending: after merge and production deployment, reload the actual MCP tool interface and verify criteria updates, key lookup and an allowed status transition on a dedicated test card. Local HTTP tests verify this flow but do not replace the requested production check. KAN-67 is outside this change.
KAN-72 lets agents refine existing tickets entirely through MCP: `update_ticket` edits all supported ticket fields and the real acceptance checklist, `get_ticket` accepts an exact ticket key, and paginated search/project discovery plus compact current workflow configuration provide the required IDs without scanning status lists.
Updates reuse the existing UI validation, transactional action, worklog and notification behavior. Omitted fields remain unchanged, nullable scalar `null` clears values, and supplied checklist/custom-field lists replace the list (`[]` clears it). Existing checklist IDs remain stable; new entries get new IDs, and foreign/duplicate IDs are rejected. Workflow changes continue through `move_ticket_status`. Existing tools remain compatible.
Validation: affected MCP, project-ticket controller and API tests pass; frontend build and PHP formatting pass. Regression coverage includes application-key HTTP refinement, permission-scoped pagination, parent/author/person rules, checklist identity and rollback. The PR targets its recorded base `main` (ba12e65).
Production acceptance is still pending: after merge and production deployment, reload the actual MCP tool interface and verify criteria updates, key lookup and an allowed status transition on a dedicated test card. Local HTTP tests verify this flow but do not replace the requested production check. KAN-67 is outside this change.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
KAN-72 lets agents refine existing tickets entirely through MCP:
update_ticketedits all supported ticket fields and the real acceptance checklist,get_ticketaccepts an exact ticket key, and paginated search/project discovery plus compact current workflow configuration provide the required IDs without scanning status lists.Updates reuse the existing UI validation, transactional action, worklog and notification behavior. Omitted fields remain unchanged, nullable scalar
nullclears values, and supplied checklist/custom-field lists replace the list ([]clears it). Existing checklist IDs remain stable; new entries get new IDs, and foreign/duplicate IDs are rejected. Workflow changes continue throughmove_ticket_status. Existing tools remain compatible.Validation: affected MCP, project-ticket controller and API tests pass; frontend build and PHP formatting pass. Regression coverage includes application-key HTTP refinement, permission-scoped pagination, parent/author/person rules, checklist identity and rollback. The PR targets its recorded base
main(ba12e65).Production acceptance is still pending: after merge and production deployment, reload the actual MCP tool interface and verify criteria updates, key lookup and an allowed status transition on a dedicated test card. Local HTTP tests verify this flow but do not replace the requested production check. KAN-67 is outside this change.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.