View as Markdown
Jira icon

Jira ACTION

Transition Issue

Performs an issue transition and, if the transition has a screen, updates the fields from the transition screen. See the documentation
  • Action
  • Writes data
  • Destructive
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run Transition 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-transition-issue",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    issueIdOrKey: "Issue ID or Key",
  },
})

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.

Transition Issue inputs
Property Type Description
cloudId Cloud ID string
The Jira Cloud site ID (for example, 11223344-a1b2-3b33-c444-def123456789). Use Get Cloud ID to discover IDs. See the documentation
Required Dynamic
issueIdOrKey Issue ID or Key string
The ID or key of an issue
Required Dynamic
transition Transition ID string
The string ID of the transition to perform (e.g. "11"). Use the id value returned by the Get Transitions action.
Required Dynamic
fields Fields object
List of issue screen fields to update, specifying the sub-field to update and its value for each field. This field provides a straightforward option when setting a sub-field. When multiple sub-fields or other operations are required, use update. Fields included in here cannot be included in update. (.i.e for Fields "fields": {"summary":"Completed orders still displaying in pending","customfield_10010":1,}) see doc
Optional
update Update object
List of operations to perform on issue screen fields. Note that fields included here cannot be included in fields.
Optional
historyMetadata History Metadata object
Additional issue history details. See HistoryMetadata section of doc
Optional
properties Properties string
Details of issue properties to be add or update
Optional
additionalProperties Additional Properties object
Extra properties of any type may be provided to this object
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-transition-issue
Version
0.1.28
App
Jira
Authentication
OAuth
Read-only
No
Destructive
Yes
Open world
Yes