Jira ACTION
Create Issue
Creates an issue or, where the option to create subtasks is enabled in Jira, a subtask. See the documentation
- Action
- Writes data
- OAuth
- SDK
- MCP
IMPLEMENTATION
Call this tool
Connect a user's Jira account once, then configure and run Create 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-create-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-create-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-create-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 (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 |
updateHistory Update History | boolean | Whether the project in which the issue is created is added to the user's Recently viewed project list, as shown under Projects in Jira Optional |
projectId Project ID | string | The ID of the project the issue will be created in. Use the Get All Projects action to look up project IDs. Required |
issueTypeId Issue Type | string | An ID identifying the type of issue to create. Use the Get Issue Types action to look up issue type IDs for the project. Required |
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. Required — at least one field (e.g. summary) must be provided to create the issue. Required |
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-create-issue
- Version
- 1.0.0
- App
- Jira
- Authentication
- OAuth
- Read-only
- No
- Destructive
- No
- Open world
- Yes
- Source
- View on GitHub ↗