Jira

The Jira pack provides 4 nodes for interacting with Jira Cloud. Use these nodes to create issues, search with JQL, retrieve issue details, and add comments from your automation patterns.

Connection setup

Jira requires three credential fields. DRAGOPS displays a form with all three fields when you set up the connection.

1. Go to the Connections page in the DRAGOPS dashboard.
2. Select Jira from the provider list.
3. Enter the following credentials:
   • Jira User Email — the email address associated with your Atlassian account
   • Jira API Token — generate one at id.atlassian.com/manage-profile/security/api-tokens
   • Jira Base URL — your Jira Cloud instance URL (for example, https://mycompany.atlassian.net)
4. Select Save.

DRAGOPS uses basic authentication (email + API token) for all Jira API requests. The base URL is resolved from your connection credentials at execution time, so each connection can point to a different Jira Cloud instance.

Available nodes

All Jira nodes are in the Jira category in the node library.

Every node also has execution pins (exec in and exec out) for controlling the execution flow.

Output data

The Issue output pin from Get Issue returns the complete Jira issue object, including fields like summary, status, assignee, priority, and description. Use Get Property nodes to extract specific fields. For example, to get the issue summary, use Get Property with the key fields.summary.

The Issues output pin from Search Issues returns an array of issue objects matching the JQL query. The Total pin returns the total number of matching issues (which may be more than the returned page).

Example: Create an issue from a webhook

This pattern receives a webhook event and creates a Jira issue with the event data:

1. Add an On Webhook trigger node.
2. Add Get Property nodes to extract projectKey, summary, and description from the webhook body.
3. Add a Create Issue node from the Jira category. Wire the extracted values to the Project Key, Summary, and Description input pins. Set the Issue Type input to "Task" using a String literal node.
4. Add a Log node. Wire Create Issue's Issue Key output to Log's Message input to confirm the issue was created.
5. Wire the execution flow through all nodes.

Send a POST request to the webhook URL:

{
  "projectKey": "OPS",
  "summary": "Alert: High CPU on web-01",
  "description": "CPU usage exceeded 90% for 5 minutes."
}

The pattern creates a Jira issue in the OPS project and logs the new issue key (for example, OPS-142).

Tips

• JQL syntax. The Search Issues node accepts any valid JQL query. Common examples: project = OPS AND status = Open, assignee = currentUser() ORDER BY created DESC, labels = bug AND created >= -7d. See the Atlassian JQL reference for the full syntax.
• Issue type names. The Issue Type input expects the display name, not an ID. Common values are Task, Bug, Story, Epic, and Sub-task. Names are case-sensitive.
• Description format. The Create Issue node automatically wraps plain text in Atlassian Document Format. You do not need to construct ADF manually — pass a plain text string and the node handles the conversion.
• Max Results. The Search Issues node defaults to the Jira API's page size (50) if Max Results is not wired. To retrieve more results, wire an integer value to the Max Results pin (maximum 100 per request).

Related

• VirusTotal — threat intelligence integration pack
• Integration packs — how packs work
• Connect external services — credential storage and the connections system
• Use integration pack nodes — step-by-step guide for using pack nodes