View as Markdown
Jira icon

Jira ACTION

Move Issues to Sprint

Moves issues to a sprint, for a given sprint ID. 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 Move Issues to Sprint 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-move-issues-to-sprint",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    boardId: "Board ID",
  },
})

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.

Move Issues to Sprint 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
boardId Board ID string
The ID of the board
Required Dynamic
sprintId Sprint ID string
The ID of the sprint
Required Dynamic
issues Issues string[]
The IDs or keys of the issues to move to the sprint.
Required Dynamic

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-move-issues-to-sprint
Version
0.0.8
App
Jira
Authentication
OAuth
Read-only
No
Destructive
Yes
Open world
Yes