View as Markdown
Jira icon

Jira ACTION

Search Issues with JQL (POST)

Searches for issues using JQL with enhanced search capabilities. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run Search Issues with JQL (POST) 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-search-issues-with-jql-post",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    jql: "JQL Query",
  },
})

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.

Search Issues with JQL (POST) 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
jql JQL Query string
The JQL that defines the search. If no JQL expression is provided, all issues are returned. Note: username and userkey cannot be used as search terms due to privacy reasons. Use accountId instead
Required
maxResults Max Results integer
The maximum number of items to return per page
Optional
nextPageToken Next Page Token string
Token for pagination. Use the token from a previous response to get the next page of results
Optional
fields Fields string[]
A list of fields to return for each issue. Use it to retrieve a subset of fields. Examples: summary,comment or *all,-comment
Optional
expand Expand string[]
Use expand to include additional information about issues in the response
Optional
properties Properties string[]
A list of issue property keys for issue properties to include in the results. A maximum of 5 issue property keys can be specified
Optional
fieldsByKeys Fields By Keys boolean
Reference fields by their key (rather than ID)
Optional
reconcileIssues Reconcile Issues string[]
A list of issue IDs or keys to reconcile for read-after-write consistency. This ensures that recently created or updated issues are included in the search results
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-search-issues-with-jql-post
Version
0.0.10
App
Jira
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes