targetprocess-mcp-server 2.0.3 → 2.0.4

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 (2) hide show
  1. package/build/index.js +3 -3
  2. package/package.json +1 -1
package/build/index.js CHANGED
@@ -597,8 +597,8 @@ server.registerTool('create_bug_based_on_card', {
597
597
  CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
598
598
  1) IF you already have user story or bug card content, proceed to step 3 skipping step 2;
599
599
  2) ELSE call "get_user_story_content" tool or "get_bug_content" tool to get user story or bug card content;
600
- 3) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior;
601
- 4) add a comment to the card with bug Id provided in the first step and Title`,
600
+ 3) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>);
601
+ 4) add a comment to the card with created bug Id and its Title`,
602
602
  inputSchema: {
603
603
  title: z.string()
604
604
  .describe('Bug card title that summarizes the problem in concise, descriptive, and actionable manner, enabling a developer to understand the issue without opening the report'),
@@ -652,7 +652,7 @@ server.registerTool('create_bug', {
652
652
  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.
653
653
  NOTE: this tool does not require a user story or bug card referenced.
654
654
  CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
655
- 1) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior;
655
+ 1) format the new bug inside html <div> tags with Issue Description, Steps to Reproduce, Expected Behavior, Actual Behavior sections (note: section titles should be wrapped in <h3> tags, e.g. <h3>Issue Description</h3>);
656
656
  2) add a comment to the newly created bug with its Id and Title`,
657
657
  inputSchema: {
658
658
  title: z.string()
package/package.json CHANGED
@@ -25,7 +25,7 @@
25
25
  "engines": {
26
26
  "node": ">=20.x"
27
27
  },
28
- "version": "2.0.3",
28
+ "version": "2.0.4",
29
29
  "description": "MCP server for Tartget Process",
30
30
  "main": "build/index.js",
31
31
  "keywords": [