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
- Destructive
- 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)curl -X POST https://api.pipedream.com/v1/connect/{project_id}/actions/run \
-H "Content-Type: application/json" \
-H "X-PD-Environment: production" \
-H "Authorization: Bearer {access_token}" \
-d '{
"external_user_id": "{external_user_id}",
"id": "jira-update-issue",
"configured_props": {
"jira": { "authProvisionId": "apn_xxxxxxx" },
"cloudId": "Cloud ID",
"historyMetadata": "History Metadata"
}
}'// accessToken: mint a short-lived token with the Connect SDK — see the MCP guide
const transport = new StreamableHTTPClientTransport(
new URL("https://remote.mcp.pipedream.net/v3"),
{
requestInit: {
headers: {
Authorization: `Bearer ${accessToken}`,
"x-pd-project-id": "{project_id}",
"x-pd-environment": "production",
"x-pd-external-user-id": "{external_user_id}", // any stable ID for this user in your system
"x-pd-app-slug": "jira",
},
},
},
)
const mcp = new Client({ name: "my-agent", version: "1.0.0" })
await mcp.connect(transport)
const { tools } = await mcp.listTools()
// listTools() hands your model this tool's input schema, so it can
// fill the arguments itself:
const result = await mcp.callTool({
name: "jira-update-issue",
arguments: {
cloudId: "Cloud ID",
historyMetadata: "History Metadata",
},
})SCHEMA
Inputs
Pipedream supplies the connected account. Your application provides the operation-specific values below. Dynamic inputs are resolved against that user's account.
| 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 |
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 | A Map containing the field name and a list of operations to perform on the issue screen field. Note that fields included here cannot be included in fields. Optional |
additionalProperties Additional properties | object | Extra properties of any type may be provided to this object Optional |
projectId Project ID | string | The project ID Required Dynamic |
issueIdOrKey Issue ID or Key | string | The ID or key of an issue Required Dynamic |
issueTypeId Issue Type | string | An ID identifying the type of issue. Check the API docs to see available options Optional Dynamic |
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. Retrieving options requires a static issueIdOrKey. Required when specifying a transition to undertake. Optional Dynamic |
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
- 0.3.1
- App
- Jira
- Authentication
- OAuth
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗