@rui.branco/jira-mcp 1.7.8 → 1.7.10

package/index.js

@@ -474,9 +474,12 @@ async function fetchJira(endpoint, options = {}, instance = defaultInstance) {
   });
   if (!response.ok) {
     const errorBody = await response.text().catch(() => "");
-    throw new Error(
+    const error = new Error(
       `Jira API error: ${response.status} ${response.statusText}${errorBody ? ` - ${errorBody}` : ""}`,
     );
+    error.status = response.status;
+    error.body = errorBody;
+    throw error;
   }
   const text = await response.text();
   return text ? JSON.parse(text) : {};
@@ -810,6 +813,10 @@ function quoteText(text) {
     .join("\n");
 }
 
+// Appended to comment-tool responses so the client relays the posted text to the user
+const ECHO_DIRECTIVE =
+  "IMPORTANT: In your reply to the user, reproduce the blockquoted comment above verbatim (keep the > blockquote) so they see exactly what was posted to Jira. Never reply with just 'comment posted' or a summary of it.";
+
 // ============ USER SEARCH & MENTIONS ============
 
 // Cache for user lookups to avoid repeated API calls
@@ -2043,6 +2050,8 @@ const SERVER_INSTRUCTIONS = `# jira-mcp usage rules
 ${confluenceMode !== "always" ? "- Confluence tools are hidden until activated: call `confluence_enable` first when a task needs Confluence (pages, spaces, page comments, labels, attachments).\n" : ""}
 ## Writing Jira comments (jira_add_comment / jira_reply_comment / jira_edit_comment)
 Write one short conversational paragraph: start with @DisplayName of who to notify (NOT [~accountId:...] syntax), say what changed, and end with the next step (e.g. 'Ready for verification.'). Keep it HIGH LEVEL for stakeholders/PO/QA — WHAT changed and the impact, not how it was built. Include technical detail (endpoints, payloads, API contracts) ONLY when the reader is a developer and it makes sense; otherwise leave out code, file paths, branch names, commit hashes, and framework-internal terms. NEVER use em dashes (—) or en dashes (–) — use commas, periods, or rewrite. Avoid bullet lists, headings, and bold unless the update genuinely needs them.
+Do NOT @mention automation/service accounts (e.g. 'Jira Integrations', bots): when the reporter or notify target is one, write the comment without any mention.
+After the tool succeeds, its response echoes the posted comment as a markdown blockquote. ALWAYS reproduce that blockquote verbatim in your final reply to the user so they see exactly what was posted to Jira — never reply with just 'comment added' or a paraphrase.
 
 ## Writing descriptions (jira_create_ticket / jira_update_ticket / jira_create_subtask)
 Structure with Markdown: a one/two-sentence overview, then ## / ### headings (Overview, Details, Acceptance Criteria), '-' bullet lists, numbered steps, tables for structured data, **bold** key terms, fenced \`\`\` blocks for code/payloads. Blank line between blocks. Concise and scannable. Never use em/en dashes.`;
@@ -2345,7 +2354,7 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
       {
         name: "jira_search_users",
         description:
-          "Search for Jira users by name or email. Returns account IDs and display names. Use this to find users for mentions or assignments. When multiple Jira instances are configured, use the 'instance' parameter to specify which one.",
+          "Search for Jira users by name or email. Returns account IDs and display names. Use this to find users for mentions or assignments. For assignment-oriented searches, provide issueKey or projectKey to find users assignable to that issue or project when global user browsing is unavailable. When multiple Jira instances are configured, use the 'instance' parameter to specify which one.",
         inputSchema: {
           type: "object",
           properties: {
@@ -2358,6 +2367,16 @@ server.setRequestHandler(ListToolsRequestSchema, async () => {
               type: "number",
               description: "Max results (default 5)",
             },
+            issueKey: {
+              type: "string",
+              description:
+                "Optional issue key for assignment-oriented searches (e.g., 'MODS-123'). If global user search is empty or user browsing is forbidden, search users assignable to this issue. The instance is auto-detected from the issue key when omitted.",
+            },
+            projectKey: {
+              type: "string",
+              description:
+                "Optional project key for assignment-oriented searches (e.g., 'MODS'). If global user search is empty or user browsing is forbidden, search users assignable to this project. Used when issueKey is not provided.",
+            },
             instance: {
               type: "string",
               description: "Instance name (optional).",
@@ -3499,13 +3518,45 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         ],
       };
     } else if (name === "jira_search_users") {
-      const inst = getInstanceByName(args.instance);
+      const inst = resolveInstanceForTool(name, args);
       const maxResults = args.maxResults || 5;
-      const users = await fetchJira(
-        `/user/search?query=${encodeURIComponent(args.query)}&maxResults=${maxResults}`,
-        {},
-        inst,
-      );
+      const hasAssignmentContext = Boolean(args.issueKey || args.projectKey);
+      let users;
+      let useAssignableFallback = false;
+
+      try {
+        users = await fetchJira(
+          `/user/search?query=${encodeURIComponent(args.query)}&maxResults=${maxResults}`,
+          {},
+          inst,
+        );
+      } catch (error) {
+        const errorDetail = String(error.body || error.message || "").toLowerCase();
+        if (
+          hasAssignmentContext &&
+          error.status === 403 &&
+          /(browse users|user browsing|users and groups)/.test(errorDetail)
+        ) {
+          useAssignableFallback = true;
+        } else {
+          throw error;
+        }
+      }
+
+      if (
+        useAssignableFallback ||
+        (hasAssignmentContext && (!users || users.length === 0))
+      ) {
+        const scope = args.issueKey
+          ? `issueKey=${encodeURIComponent(args.issueKey)}`
+          : `project=${encodeURIComponent(args.projectKey)}`;
+        users = await fetchJira(
+          `/user/assignable/search?${scope}&query=${encodeURIComponent(args.query)}&maxResults=${maxResults}`,
+          {},
+          inst,
+        );
+      }
+
       if (!users || users.length === 0) {
         return {
           content: [
@@ -3612,7 +3663,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         content: [
           {
             type: "text",
-            text: `Comment added to ${args.issueKey} by ${author} at ${created}:\n\n${postedText}`,
+            text: `Comment added to ${args.issueKey} by ${author} at ${created}:\n\n${postedText}\n\n${ECHO_DIRECTIVE}`,
           },
         ],
       };
@@ -3681,7 +3732,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         content: [
           {
             type: "text",
-            text: `Reply to ${originalAuthor}'s comment posted on ${args.issueKey} by ${author} at ${created}:\n\n${postedText}`,
+            text: `Reply to ${originalAuthor}'s comment posted on ${args.issueKey} by ${author} at ${created}:\n\n${postedText}\n\n${ECHO_DIRECTIVE}`,
           },
         ],
       };
@@ -3706,7 +3757,7 @@ server.setRequestHandler(CallToolRequestSchema, async (request) => {
         content: [
           {
             type: "text",
-            text: `Comment ${args.commentId} on ${args.issueKey} updated:\n\n${editedText}`,
+            text: `Comment ${args.commentId} on ${args.issueKey} updated:\n\n${editedText}\n\n${ECHO_DIRECTIVE}`,
           },
         ],
       };

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@rui.branco/jira-mcp",
-  "version": "1.7.8",
+  "version": "1.7.10",
   "description": "Jira & Confluence MCP server for any MCP-compatible AI client (Claude Code, Codex, Antigravity, Cursor, etc.) - fetch tickets, search with JQL, update tickets, manage comments, change status, get Figma designs. Optional per-tool scopes, dry-run, audit log, and rate limiting.",
   "main": "index.js",
   "bin": {