Skip to main content
Glama

jira_update_issue_advanced

Update Jira issues comprehensively by modifying summary, description, priority, assignee, labels, components, fixVersions, affectsVersions, and custom fields. Use jira_get_edit_meta first to discover editable fields and allowed values.

Instructions

Update a Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_edit_meta first to discover editable fields and allowed values.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
issueKeyYesThe Jira issue key
summaryNoNew summary
descriptionNoNew description
priorityNoNew priority name
assigneeNoNew assignee username
labelsNoNew labels
componentsNoComponent names
fixVersionsNoFix version names
affectsVersionsNoAffects version names
customFieldsNoCustom fields as key-value pairs

Implementation Reference

  • The main handler for the jira_update_issue_advanced tool. Parses input arguments using Zod schema, constructs the fields object for update (handling components, versions, custom fields), calls jiraClient.updateIssueRaw, and returns success message.
    case "jira_update_issue_advanced": {
      const {
        issueKey,
        summary,
        description,
        priority,
        assignee,
        labels,
        components,
        fixVersions,
        affectsVersions,
        customFields,
      } = UpdateIssueAdvancedSchema.parse(args);
    
      const fields: Record<string, unknown> = {};
    
      if (summary) fields.summary = summary;
      if (description) fields.description = description;
      if (priority) fields.priority = { name: priority };
      if (assignee) fields.assignee = { name: assignee };
      if (labels) fields.labels = labels;
      if (components)
        fields.components = components.map((name) => ({ name }));
      if (fixVersions)
        fields.fixVersions = fixVersions.map((name) => ({ name }));
      if (affectsVersions)
        fields.versions = affectsVersions.map((name) => ({ name }));
    
      // Merge custom fields
      if (customFields) {
        Object.assign(fields, customFields);
      }
    
      await jiraClient.updateIssueRaw(issueKey, fields);
      return {
        content: [
          { type: "text", text: `Issue ${issueKey} updated successfully` },
        ],
      };
    }
  • Zod schema used for input validation in the tool handler. Defines structure and descriptions for all parameters including customFields.
    const UpdateIssueAdvancedSchema = z.object({
      issueKey: z.string().describe("The Jira issue key"),
      summary: z.string().optional().describe("New summary"),
      description: z.string().optional().describe("New description"),
      priority: z.string().optional().describe("New priority name"),
      assignee: z.string().optional().describe("New assignee username"),
      labels: z.array(z.string()).optional().describe("New labels"),
      components: z.array(z.string()).optional().describe("Component names"),
      fixVersions: z.array(z.string()).optional().describe("Fix version names"),
      affectsVersions: z
        .array(z.string())
        .optional()
        .describe("Affects version names"),
      customFields: z
        .record(z.unknown())
        .optional()
        .describe("Custom fields as key-value pairs"),
    });
  • src/index.ts:601-640 (registration)
    Tool registration entry in the ListTools response array, including name, description, and inputSchema matching the Zod schema.
    {
      name: "jira_update_issue_advanced",
      description:
        "Update a Jira issue with full field support including fixVersions, components, and custom fields. Use jira_get_edit_meta first to discover editable fields and allowed values.",
      inputSchema: {
        type: "object",
        properties: {
          issueKey: { type: "string", description: "The Jira issue key" },
          summary: { type: "string", description: "New summary" },
          description: { type: "string", description: "New description" },
          priority: { type: "string", description: "New priority name" },
          assignee: { type: "string", description: "New assignee username" },
          labels: {
            type: "array",
            items: { type: "string" },
            description: "New labels",
          },
          components: {
            type: "array",
            items: { type: "string" },
            description: "Component names",
          },
          fixVersions: {
            type: "array",
            items: { type: "string" },
            description: "Fix version names",
          },
          affectsVersions: {
            type: "array",
            items: { type: "string" },
            description: "Affects version names",
          },
          customFields: {
            type: "object",
            description: "Custom fields as key-value pairs",
          },
        },
        required: ["issueKey"],
      },
    },
  • Core helper method in JiraClient that performs the actual Jira REST API PUT request to update the issue with arbitrary fields.
    async updateIssueRaw(
      issueKey: string,
      fields: Record<string, unknown>
    ): Promise<void> {
      await this.request<void>(`/issue/${issueKey}`, {
        method: "PUT",
        body: JSON.stringify({ fields }),
      });
    }
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries full burden. It mentions the tool updates issues with 'full field support,' implying mutation capabilities, but doesn't disclose behavioral traits like authentication requirements, rate limits, error handling, or what happens to unspecified fields. The description adds some context about field discovery but lacks comprehensive behavioral details.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two sentences with zero waste: the first states purpose and scope, the second provides critical usage guidance. It's front-loaded with essential information and appropriately sized for the tool's complexity.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (10 parameters, mutation operation, no annotations, no output schema), the description is reasonably complete. It covers purpose, distinguishes from siblings, and provides workflow guidance. However, it lacks details about return values or error conditions, which would be helpful since there's no output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents all 10 parameters thoroughly. The description mentions 'fixVersions, components, and custom fields' as examples, which aligns with schema parameters but doesn't add meaningful semantic context beyond what the schema provides. Baseline 3 is appropriate when schema does the heavy lifting.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the verb ('Update') and resource ('a Jira issue') with specific scope ('with full field support including fixVersions, components, and custom fields'). It distinguishes from the sibling 'jira_update_issue' by emphasizing 'advanced' capabilities like custom fields.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly provides when-to-use guidance: 'Use jira_get_edit_meta first to discover editable fields and allowed values.' This names a specific prerequisite tool and explains its purpose in the workflow, helping the agent choose correctly among update-related tools.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/yogeshhrathod/JiraMCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server