View as Markdown
Jira icon

Jira ACTION

Check Issues Against JQL

Checks whether one or more issues would be returned by one or more JQL queries. See the documentation
  • Action
  • Read only
  • OAuth
  • SDK
  • MCP

IMPLEMENTATION

Call this tool

Connect a user's Jira account once, then configure and run Check Issues Against JQL 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-check-issues-against-jql",
  externalUserId: "{external_user_id}", // any stable ID for this user in your system
  configuredProps: {
    jira: { authProvisionId: "apn_xxxxxxx" },
    cloudId: "Cloud ID",
    issueIds: ["Issue IDs"],
  },
})

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.

Check Issues Against JQL 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
issueIds Issue IDs string[]
A list of issue IDs to check against the JQL queries. Example: ["10001", "10042"]
Required Dynamic
jqls JQL Queries string[]
A list of JQL query strings to check the issues against. Example: ["project = FOO", "issuetype = Bug"]
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-check-issues-against-jql
Version
0.0.11
App
Jira
Authentication
OAuth
Read-only
Yes
Destructive
No
Open world
Yes