Update a user story card
update_user_storyModify a Targetprocess user story card by ID, changing only specified fields such as title, description, state, team, project, sprint, feature, or tags.
Instructions
Update a user story card with data provided 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_user_story_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;
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_user_story"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | User story card ID (e.g. 145789) | |
| tags | No | Optional comma-separated tags to apply, e.g. "regression, mobile" | |
| title | No | Updated user story title | |
| teamId | No | Optional Team ID — if user gave a team name, resolve it via "get_teams" first | |
| featureId | No | Optional Feature ID — moves this user story to the specified feature | |
| projectId | No | Optional Project ID — if user gave a project name, resolve it via "get_projects" first | |
| description | No | Updated user story description (format as HTML) | |
| entityStateId | No | Optional Entity State ID — if user gave a state name, resolve it via "get_user_story_workflows" first | |
| teamIterationId | No | Optional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first |