View as Markdown
Jira icon

Jira ACTION

Update Issue

Updates an issue. A transition may be applied and issue properties updated as part of the edit. See the documentation
  • Action
  • Writes data
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run Update Issue from your backend or agent.

import { PipedreamClient } from "@pipedream/sdk"

const pd = new PipedreamClient({
  projectId: process.env.PIPEDREAM_PROJECT_ID!,
  clientId: process.env.PIPEDREAM_CLIENT_ID!,
  clientSecret: process.env.PIPEDREAM_CLIENT_SECRET!,
  projectEnvironment: "production",
})

const result = await pd.actions.run({
  id: "jira-update-issue",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    historyMetadata: "History Metadata",
  },
})

console.log(result)

SCHEMA

Inputs

Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.

Update Issue inputs
Property Type Description
cloudId Cloud ID string
The Jira Cloud site ID (e.g., 11223344-a1b2-3b33-c444-def123456789). Use the Get Cloud ID action to look up the ID for your site.
Required
historyMetadata History Metadata object
Additional issue history details
Optional
properties Properties string
Details of issue properties to be added or updated. Please provide an array of objects with keys and values.
Optional
update Update object
Advanced: a Map of field names to a list of add/remove/set operations to perform (e.g. appending a value to a multi-value field), following Jira's issue update operations format. For setting field values directly (summary, description, priority, labels, etc.), use additionalProperties instead.
Optional
additionalProperties Additional properties object
The primary way to set issue field values not already covered by other props. Provide a flat object of Jira field keys to values, e.g. { "summary": "Fix login bug", "description": "Plain text is fine here", "priority": { "name": "High" }, "labels": ["bug"] }. description and environment may be given as plain strings — they're automatically converted to Jira's required document format. Use this instead of update for straightforward field assignments.
Optional
issueIdOrKey Issue ID or Key string
The ID or key of the issue to update (e.g. 10001 or PROJ-123). Use the Search Issues with JQL action to look up issues.
Required
notifyUsers Notify Users boolean
Whether a notification email about the issue update is sent to all watchers. To disable the notification, administer Jira or administer project permissions are required. If the user doesn't have the necessary permission the request is ignored.
Optional
overrideScreenSecurity Override Screen Security boolean
Whether screen security should be overridden to enable hidden fields to be edited. Available to Connect app users with admin permissions.
Optional
overrideEditableFlag Override Editable Flag boolean
Whether screen security should be overridden to enable uneditable fields to be edited. Available to Connect app users with admin permissions.
Optional
transitionId Transition ID string
The ID of the issue transition. Use the Get Transitions action to look up transition IDs for the issue. Required when specifying a transition to undertake.
Optional
transitionLooped Transition Looped boolean
Whether the transition is looped
Optional

REFERENCE

Tool details

Behavior hints are published with the component in the Pipedream registry and surface as MCP tool annotations, so an agent can reason about a tool before it calls it.

Registry key
jira-update-issue
Version
1.0.0
App
Jira
Authentication
OAuth
Read-only
No
Destructive
No
Open world
Yes