Create a new bug card based on provided card id
create_bug_based_on_cardCreate a detailed Targetprocess bug from an existing user story, bug, or feature card, generating a structured report with environment, steps to reproduce, expected, and actual behavior.
Instructions
Create a new bug card based on provided card id that summarizes the problem in concise, descriptive manner answering questions What? Where? When?, and content explaining what happened in detail. NOTE: this tool requires a user story, bug, or feature card as a reference (i.e. card ID). CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) IF you already have user story, bug, or feature card content, proceed to step 3 skipping step 2; 2) ELSE call "get_user_story_content" tool, "get_bug_content" tool, or fetch the feature to get card content; 3) format the new bug inside html tags with Environment (describes where bug was found, dev, feature, review or uat Environment), Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in tags, e.g. Issue Description); 4) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 5) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 6) 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; 7) add a comment to the card with created bug Id and its Title
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": {
"title": "<title>",
"card": "<card>",
"bugContent": "<bugContent>"
},
"name": "create_bug_based_on_card"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| card | Yes | ||
| title | Yes | 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" if no origin was specified | |
| 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 | Yes | Comment content to add, 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 |