Update a bug card
update_bugUpdate Targetprocess bug fields such as title, description, state, team, project, iteration, release, origin, and tags using only the values the user wants changed.
Instructions
Update a bug card with data proded from user input. NOTE: pass only the fields that user wants to update. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 2) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 3) IF the user specified a state by name (not ID), call "get_bug_workflows" to find the matching state and use its ID as entityStateId; 4) IF the user specified a sprint/iteration by name, call "get_team_iterations" to find the matching iteration and use its ID as teamIterationId; 5) IF the user specified a release by name (not ID), call "get_current_releases" to find the matching release and use its ID as releaseId;
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": {
"id": "<id>"
},
"name": "update_bug"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Bug card ID (e.g. 145789) | |
| tags | No | Optional comma-separated tags to apply, e.g. "regression, mobile" | |
| title | No | Bug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report | |
| origin | No | Where the bug was found, defaults to "Manual QA" | |
| teamId | No | Optional Team ID — if user gave a team name, resolve it via "get_teams" first; defaults to TP_TEAM_ID from config | |
| projectId | No | Optional Project ID — if user gave a project name, resolve it via "get_projects" first; defaults to TP_PROJECT_ID from config | |
| releaseId | No | Optional Release ID to assign this bug to — if user gave a release name, resolve it via "get_current_releases" first | |
| bugContent | No | Bug description content, explain what happened in detail. Include expected behaviour and what actually occurred. Be specific and avoid assumptions. Clearly outline the actions needed to trigger the bug. Number each step so anyone can follow them easily | |
| entityStateId | No | Optional Entity State ID — if user gave a state name, resolve it via "get_bug_workflows" first; defaults to "Backlog" | |
| teamIterationId | No | Optional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first |