Jira Data Center ACTION
Update Sprint Fully
Performs a full update of a sprint. A full update means that the result will be exactly the same as the request body. Any fields not present in the request JSON will be set to null. See the documentation
- Action
- Writes data
- Destructive
- API key
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Jira Data Center account once, then configure and run Update Sprint Fully 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_data_center-update-sprint-fully",
externalUserId: "{external_user_id}", // any stable ID for this user in your system
configuredProps: {
jira_data_center: { authProvisionId: "apn_xxxxxxx" },
boardId: "Board ID",
sprintId: "Sprint ID",
},
})
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_data_center-update-sprint-fully",
"configured_props": {
"jira_data_center": { "authProvisionId": "apn_xxxxxxx" },
"boardId": "Board ID",
"sprintId": "Sprint ID"
}
}'// 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_data_center",
},
},
},
)
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_data_center-update-sprint-fully",
arguments: {
boardId: "Board ID",
sprintId: "Sprint ID",
},
})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 |
|---|---|---|
boardId Board ID | string | The ID of the board Required Dynamic |
sprintId Sprint ID | string | The ID of the sprint Required Dynamic |
name Name | string | The name of the sprint Required |
state State | string | The state of the sprint Required |
startDate Start Date | string | The start date of the sprint. Format: YYYY-MM-DDTHH:MM:SS.SSSZ Required |
endDate End Date | string | The end date of the sprint. Format: YYYY-MM-DDTHH:MM:SS.SSSZ Required |
autoStartStop Auto Start Stop | boolean | Whether to automatically start and stop the sprint Optional |
goal Goal | string | The goal of the sprint Optional |
synced Synced | boolean | Whether the sprint is synced. Only Jira administrators can create synced sprints. Optional |
activatedDate Activated Date | string | The activated date of the sprint. Format: YYYY-MM-DDTHH:MM:SS.SSSZ Optional |
completedDate Completed Date | string | The completed date of the sprint. Format: YYYY-MM-DDTHH:MM:SS.SSSZ 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_data_center-update-sprint-fully
- Version
- 0.0.3
- App
- Jira Data Center
- Authentication
- API key
- Read-only
- No
- Destructive
- Yes
- Open world
- Yes
- Source
- View on GitHub ↗