targetprocess-mcp-server 2.2.9-b → 2.2.10

package/README.md

@@ -48,6 +48,10 @@ Features
 User Stories
 - `get_user_story_bugs` — Get all bugs linked to a user story by its ID (id)
 
+Tasks
+- `get_in_progress_tasks_and_bugs` — Get all Tasks and Bugs currently in "In Progress" state assigned to a given user (userId)
+- `create_task` — Create a new task linked to a user story (title, userStoryId, optional description)
+
 Cards — Read
 - `get_card_current_status` — Get EntityState, TeamState, and assigned teams for a card (id, optional resourceType: UserStory | Bug | Feature, default: UserStory)
 - `get_bug_content` — Fetch full content of a bug by ID (id)
@@ -100,6 +104,12 @@ Teams
 User
 - `get_logged_in_user` — Get the currently logged-in user's info (no params needed)
 
+Developer Tools
+- `get_commit_message` — Returns a formatted commit message string for a task or bug ID (id, type: task | bug)
+  > Format for task on a user story: `F#<featureId> US#<userStoryId> T#<taskId> <title>`
+  > Format for bug on a user story: `F#<featureId> US#<userStoryId> B#<bugId> <title>`
+  > Format for standalone bug: `B#<bugId> <title>`
+
 
 ---
 

package/build/index.js

@@ -599,10 +599,10 @@ server.registerTool('get_bug_comments', {
 server.registerTool('create_bug_based_on_card', {
     title: 'Create a new bug card based on provided card id',
     description: `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 or bug card as a reference (i.e. card ID).
+      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 or bug card content, proceed to step 3 skipping step 2;
-        2) ELSE call "get_user_story_content" tool or "get_bug_content" tool to get user story or bug card content;
+        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 <div> tags with Environment, Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior and Attachments sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>);
         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;
@@ -614,8 +614,8 @@ server.registerTool('create_bug_based_on_card', {
             id: z.string()
                 .min(5)
                 .max(6)
-                .describe(`Usually user story id or bug ID (e.g. 145789)`),
-            type: z.enum(["UserStory", "Bug"])
+                .describe(`Usually user story id, bug ID, or feature ID (e.g. 145789)`),
+            type: z.enum(["UserStory", "Bug", "Feature"])
         }),
         bugContent: z.string()
             .describe(`Comment content to add, explain what happened in detail.

package/build/tp.js

@@ -120,9 +120,10 @@ export class TpClient {
             "Description": bugContent,
         };
         if (card.type === "UserStory") {
-            bug["UserStory"] = {
-                "Id": card.id
-            };
+            bug["UserStory"] = { "Id": card.id };
+        }
+        else if (card.type === "Feature") {
+            bug["Feature"] = { "Id": card.id };
         }
         return this.post({
             pathParam: ["bugs"],

package/package.json

@@ -25,7 +25,7 @@
   "engines": {
     "node": ">=20.x"
   },
-  "version": "2.2.9b",
+  "version": "2.2.10",
   "description": "MCP server for Tartget Process",
   "main": "build/index.js",
   "keywords": [