targetprocess-mcp-server 2.2.10 → 2.2.11

package/build/index.js

@@ -603,7 +603,7 @@ server.registerTool('create_bug_based_on_card', {
       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 <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>);
+        3) format the new bug inside html <div> 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 <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;
         6) add a comment to the card with created bug Id and its Title`,
@@ -636,7 +636,7 @@ server.registerTool('create_bug_based_on_card', {
         ])
             .default("Manual QA")
             .optional()
-            .describe('Where the bug was found, defaults to "Manual QA"'),
+            .describe('Where the bug was found, defaults to "Manual QA" if no origin was specified'),
         projectId: z.string()
             .optional()
             .describe('Optional Project ID — if user gave a project name, resolve it via "get_projects" first; defaults to TP_PROJECT_ID from config'),
@@ -771,7 +771,7 @@ server.registerTool('create_bug', {
     description: `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 <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>, step to reproduce should be wrapped in <ol>);
+        1) format the new bug inside html <div> 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 <h3> tags, e.g. <h3>Issue Description</h3>, step to reproduce should be wrapped in <ol>);
         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;`,
     inputSchema: {
@@ -792,7 +792,7 @@ server.registerTool('create_bug', {
         ])
             .default("Manual QA")
             .optional()
-            .describe('Where the bug was found, defaults to "Manual QA"'),
+            .describe('Where the bug was found, defaults to "Manual QA" if no origin was specified'),
         projectId: z.string()
             .optional()
             .describe('Optional Project ID — if user gave a project name, resolve it via "get_projects" first; defaults to TP_PROJECT_ID from config'),
@@ -1481,9 +1481,9 @@ server.registerTool('get_bug_workflows', {
 });
 server.registerTool('get_user_story_workflows', {
     title: 'Get User Story workflows',
-    description: 'Get all Targetprocess user story workflows',
+    description: 'Get all Targetprocess user story workflows, with sub-states',
 }, async ({}) => {
-    const response = await tp.getUserStoryWorkflows();
+    const response = await tp.getUserStoryWorkflowsWithSubStates();
     if (!response) {
         return {
             content: [{
@@ -1501,12 +1501,13 @@ server.registerTool('get_user_story_workflows', {
                 }],
         };
     }
-    const workflows = items.map((w) => ({
+    const userStoryWorkflows = items.filter((w) => w.entityType.name === "UserStory");
+    const workflows = userStoryWorkflows.map((w) => ({
         id: w.id,
-        name: w.name,
-        processId: w.process,
-        entityType: w.entityType,
-        entityStates: w.entityStates.map((es) => ({
+        processId: w.workflow.process.id,
+        entityType: w.entityType.name,
+        entityState: w.name,
+        entitySubStates: w.subEntityStates.map((es) => ({
             id: es.id,
             name: es.name,
         })),

package/build/tp.js

@@ -562,6 +562,18 @@ export class TpClient {
             apiVersion: this.v2
         });
     }
+    async getUserStoryWorkflowsWithSubStates() {
+        return this.get({
+            pathParam: ["EntityState"],
+            param: {
+                "format": "json",
+                "select": `{id,name,isInitial,isFinal,isDefaultFinal,isPlanned,workflow:{workflow.id,process:{workflow.process.id}},entityType:{entityType.name},subEntityStates:subEntityStates.Select({id,name,entityType:{entityType.name},isInitial,isFinal,isDefaultFinal,isPlanned})}`,
+                "where": `(parentEntityState==null and workflow.process.id in [${config.tp.processId}])`,
+                "take": "1000",
+            },
+            apiVersion: this.v2
+        });
+    }
     async getBugWorkflows() {
         return this.get({
             pathParam: ["workflow"],

package/package.json

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