Create a new bug card
create_bugCreate a new Targetprocess bug card with a concise title and structured HTML details covering environment, issue description, reproduction steps, expected behavior, and actual behavior.
Instructions
Create a new bug card that summarizes the problem in concise, descriptive manner answering questions "What? Where? When?" and content explaining what happened in detail. NOTE: this tool does not require a user story or bug card reference. CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps: 1) 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, step to reproduce should be wrapped in ); 2) IF the user specified a team by name (not ID), call "get_teams" to find the matching team and use its ID as teamId; 3) IF the user specified a project by name (not ID), call "get_projects" to find the matching project and use its ID as projectId; 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": {
"title": "<title>",
"bugContent": "<bugContent>"
},
"name": "create_bug"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| tags | No | Optional comma-separated tags to apply, e.g. "regression, mobile" | |
| 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 | 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" or "To Do" | |
| teamIterationId | No | Optional Team Iteration (sprint) ID — resolve it via "get_team_iterations" first |