npm - targetprocess-mcp-server - Versions diffs - 2.6.3 → 2.6.4-a - Mend

targetprocess-mcp-server 2.6.3 → 2.6.4-a

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (4) hide show

package/build/handlers/get_feature_comments.js +45 -0
package/build/index.js +61 -3
package/build/tp.js +10 -0
package/package.json +1 -1

package/build/handlers/get_feature_comments.js ADDED Viewed

@@ -0,0 +1,45 @@
+import { JSDOM } from 'jsdom';
+export async function handleGetFeatureComments(tp, id, results) {
+    const response = await tp.getFeatureComments(id, results);
+    if (!response) {
+        return {
+            content: [{
+                    type: 'text',
+                    text: `Failed to get comments for feature id: ${id}`
+                }],
+        };
+    }
+    const items = response.Items || [];
+    if (items.length === 0) {
+        return {
+            content: [{
+                    type: 'text',
+                    text: `No comments found for feature id: ${id}`,
+                }],
+        };
+    }
+    try {
+        const parsedItems = items.map((item) => {
+            const dom = new JSDOM(`<html><body><div id="content">${item.Description}</div></body></html>`);
+            const descriptionText = dom.window.document.getElementById('content')?.textContent;
+            return {
+                id: item.Id,
+                description: descriptionText,
+                createDate: item.CreateDate,
+                owner: item.Owner.FullName,
+            };
+        });
+        return {
+            content: [{ type: 'text', text: JSON.stringify(parsedItems) }],
+        };
+    }
+    catch (error) {
+        console.error('Error parsing feature comments:', error);
+        return {
+            content: [{
+                    type: 'text',
+                    text: `Failed to parse feature comments for feature id: ${id}`,
+                }],
+        };
+    }
+}

package/build/index.js CHANGED Viewed

@@ -43,6 +43,7 @@ import { handleLogTime } from "./handlers/log_time.js";
 import { handleGetMyTimeLogs } from "./handlers/get_my_time_logs.js";
 import { handleGetFeatureUserStories } from "./handlers/get_feature_user_stories.js";
 import { handleGetFeatureContent } from "./handlers/get_feature_content.js";
+import { handleGetFeatureComments } from "./handlers/get_feature_comments.js";
 import { handleGetUserStoryBugs } from "./handlers/get_user_story_bugs.js";
 import { handleGetCardCurrentStatus } from "./handlers/get_card_current_status.js";
 import { handleUpdateUserStorySubState } from "./handlers/update_user_story_sub_state.js";
@@ -449,7 +450,7 @@ server.registerTool('update_bug', {
             .describe('Optional Team ID — if user gave a team name, resolve it via "get_teams" first; defaults to TP_TEAM_ID from config'),
         entityStateId: z.string()
             .optional()
-            .describe('Optional Entity State ID — if user gave a state name, resolve it via "get_bug_workflows" first; defaults to "Done"'),
+            .describe('Optional Entity State ID — if user gave a state name, resolve it via "get_bug_workflows" first; defaults to "Backlog"'),
         tags: z.string()
             .optional()
             .describe('Optional comma-separated tags to apply, e.g. "regression, mobile"'),
@@ -718,7 +719,12 @@ server.registerTool('create_formatted_feature', {
         1) Header — "businessBackground" is a 1-2 sentence value statement: who benefits and why;
         2) Definitions — cross-cutting terms used across multiple child stories, so they aren't redefined at every story level; if none apply, OMIT "definitions" entirely (do not send an empty section);
         3) Scope & Boundaries — what this feature explicitly includes/excludes, to stop child stories drifting into adjacent features; omit if genuinely trivial;
-        4) Non-Functional Requirements ("nonFunctionalRequirements") — every NFR category (Security, Compliance, Billing, Operational, etc.) MUST be converted from prose into one row with status "Covered" (link the child story/scenario that proves it in storyOrOwner), "Gap" (no story covers it yet — storyOrOwner names who should follow up), or "Decision needed" (genuinely still open, not testable until resolved). This is the core of the template — never leave an NFR as untested prose;
+        4) Non-Functional Requirements ("nonFunctionalRequirements") — this is the core of the template and doubles as ISO 27001:2022 audit evidence that NFRs (including information security, per Annex A Control 5.8) are considered at design time, not bolted on after. EVERY feature MUST include these four fixed rows, worded exactly as below (do not reword the questions — consistency in the questions is what makes them auditable), each answered SPECIFICALLY for this feature in "storyOrOwner" — a real, checkable answer (e.g. which systems/data/roles are involved), never a generic "considered" placeholder:
+           - area "System performance" / requirement "What does this feature add or change in terms of load, queries, polling, rendering etc., and what's the expected impact, if any?";
+           - area "Information security (ISO 27001:2022 Annex A 5.8)" / requirement "What personal or sensitive data does this feature touch, and what protects its privacy, confidentiality, integrity and availability?";
+           - area "Quality control" / requirement "How will this feature's behaviour and failures be measured or tested, and what happens when it fails?";
+           - area "Service logging" / requirement "What events or states should be logged so product support can diagnose an issue without reproducing it manually?";
+           For each row, set status to "Covered" (storyOrOwner holds the specific answer, or the child story/scenario that proves it), "Gap" (no answer/story yet — storyOrOwner names who should follow up), or "Decision needed" (genuinely open, not answerable yet). If any of the four is unclear, follow-up owner in rather than guessing — he's the named escalation contact, not a mandatory sign-off gate. Additional NFR categories beyond these four (Compliance, Billing, Operational, etc.) can still be added as extra rows when relevant, using the same Covered/Gap/Decision-needed treatment;
         5) Cross-Cutting Scenarios — ONLY for behavior spanning multiple child stories that wouldn't naturally sit in any one of them (e.g. tenant isolation across all stories); do not duplicate per-story Gherkin here; omit if none apply;
         6) Child Stories ("childStories") — pull this from "get_feature_user_stories" / "get_not_covered_user_stories_in_feature" rather than retyping it; keep it as a live pointer, not a duplicate spec; normally empty when first creating the feature;
         7) Open Questions / Risks ("openQuestions") — anything raised at feature conception that hasn't been resolved into either a Covered NFR row or a child story; this is the section most likely to get silently dropped — treat it as the running "not done yet" list until each line is promoted to a Covered NFR row;
@@ -770,7 +776,7 @@ server.registerTool('create_formatted_feature', {
                 .describe('If Covered, the child story ID/scenario that proves it; if Gap or Decision needed, who owns the follow-up (e.g. "Needs legal/BA follow-up")'),
         }))
             .min(1)
-            .describe('Every NFR category converted from prose into a testable/decided row — the core of this template. Do not leave requirements as untested prose'),
+            .describe('Every NFR category converted from prose into a testable/decided row — the core of this template. MUST include the four fixed rows required for ISO 27001:2022 audit evidence: "System performance", "Information security (ISO 27001:2022 Annex A 5.8)", "Quality control", and "Service logging" — worded exactly, each answered specifically for this feature (escalate unclear items to story owner). Additional categories may be added beyond these four. Do not leave requirements as untested prose'),
         crossCuttingScenarios: z.array(z.object({
             name: z.string()
                 .describe('Scenario name'),
@@ -1099,6 +1105,58 @@ server.registerTool('get_feature_content', {
             .describe('TP feature ID (e.g. 145636)'),
     },
 }, async ({ id }) => handleGetFeatureContent(tp, id));
+server.registerTool('get_feature_comments', {
+    title: 'Get feature comments',
+    description: 'Get comments for a TP feature by its ID',
+    inputSchema: {
+        id: z.string()
+            .min(5)
+            .max(9)
+            .describe('TP feature ID (e.g. 145636)'),
+        results: z.number()
+            .default(25)
+            .optional()
+            .describe('Number of comments to return, default is 25'),
+    },
+}, async ({ id, results }) => handleGetFeatureComments(tp, id, results));
+server.registerTool('get_assignment_roles', {
+    title: 'Get assignment roles',
+    description: 'Returns all available assignment roles (e.g. Business Analyst, Developer) with their IDs.',
+    inputSchema: {},
+}, async () => {
+    const result = await tp.getAssignmentRoles();
+    return {
+        content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
+    };
+});
+server.registerTool('assign_role', {
+    title: 'Assign a role to a user on a card',
+    description: 'Assigns a user to a specific role on a single TP card (User Story, Bug, etc.).',
+    inputSchema: {
+        cardId: z.string().describe('TP card ID (e.g. 149350)'),
+        userId: z.string().describe('TP user ID'),
+        roleId: z.string().describe('TP role ID — use get_assignment_roles to find the right ID'),
+    },
+}, async ({ cardId, userId, roleId }) => {
+    const result = await tp.assignRole(cardId, userId, roleId);
+    return {
+        content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
+    };
+});
+server.registerTool('assign_role_to_feature', {
+    title: 'Assign a role to a user on all user stories in a feature',
+    description: 'Assigns a user to a specific role on every user story within a given feature.',
+    inputSchema: {
+        featureId: z.string().describe('TP feature ID (e.g. 149341)'),
+        userId: z.string().describe('TP user ID'),
+        roleId: z.string().describe('TP role ID — use get_assignment_roles to find the right ID'),
+    },
+}, async ({ featureId, userId, roleId }) => {
+    const result = await tp.assignRoleToAllStoriesInFeature(featureId, userId, roleId);
+    return {
+        content: [{ type: "text", text: JSON.stringify(result, null, 2) }]
+    };
+});
 server.registerTool('get_user_story_bugs', {
     title: 'Get user story bugs',
     description: 'Get bugs linked to a TP user story by its ID',

package/build/tp.js CHANGED Viewed

@@ -586,6 +586,16 @@ export class TpClient {
         });
         return response;
     }
+    async getFeatureComments(featureId, results = 25) {
+        const response = await this.get({
+            pathParam: ["Features", featureId, "Comments"],
+            param: {
+                "format": "json",
+                "take": results,
+            }
+        });
+        return response;
+    }
     async searchContainsNameText({ text, entityType }) {
         return this.get({
             pathParam: [entityType],

package/package.json CHANGED Viewed

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