targetprocess-mcp-server 2.2.6 → 2.2.7-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.
- package/build/index.js +2 -2
- package/package.json +1 -1
package/build/index.js
CHANGED
|
@@ -603,7 +603,7 @@ server.registerTool('create_bug_based_on_card', {
|
|
|
603
603
|
CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
|
|
604
604
|
1) IF you already have user story or bug card content, proceed to step 3 skipping step 2;
|
|
605
605
|
2) ELSE call "get_user_story_content" tool or "get_bug_content" tool to get user story or bug card content;
|
|
606
|
-
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>);
|
|
606
|
+
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>);
|
|
607
607
|
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;
|
|
608
608
|
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;
|
|
609
609
|
6) add a comment to the card with created bug Id and its Title`,
|
|
@@ -771,7 +771,7 @@ server.registerTool('create_bug', {
|
|
|
771
771
|
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.
|
|
772
772
|
NOTE: this tool does not require a user story or bug card reference.
|
|
773
773
|
CRITICAL WORKFLOW: Before calling this tool, you MUST follow these steps:
|
|
774
|
-
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>, step to reproduce should be wrapped in <ol>);
|
|
774
|
+
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>);
|
|
775
775
|
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;
|
|
776
776
|
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;`,
|
|
777
777
|
inputSchema: {
|