Update a feature card
update_featureUpdate a Targetprocess feature card with only the fields the user wants to change, such as title, description, tags, epic, team, project, release, or sprint.
Instructions
Update a feature 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 an epic by name (not ID), resolve the epic ID first; 2) IF the user specified a release by name (not ID), call "get_current_releases" to resolve the release ID; 3) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 4) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 5) 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_feature"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Feature card ID (e.g. 145636) | |
| tags | No | Optional comma-separated tags to apply, e.g. "regression, mobile" | |
| title | No | Updated feature title | |
| epicId | No | Optional Epic ID — moves this feature to the specified epic | |
| teamId | No | Optional Team ID — if user gave a team name, resolve it via "get_teams" first | |
| projectId | No | Optional Project ID — if user gave a project name, resolve it via "get_projects" first | |
| releaseId | No | Optional Release ID to link this feature to | |
| description | No | Updated feature description (format as HTML) | |
| entityStateId | No | Optional Entity State ID — ask the user for the exact ID if given a state name; no dedicated feature-workflow lookup tool exists yet | |
| teamIterationId | No | Optional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first |