issue/create resource: issue

When to Use

• Alert-driven bug filing: A Datadog or PagerDuty alert fires on a production error. A BizFirst webhook workflow triggers issue/create to open a Bug in the OPS project, pre-filling the summary with the alert name, description with the stack trace, priority as Highest, and assigning it to the on-call rotation user — all without any human interaction.
• Support ticket escalation: A customer support system (Zendesk, Freshdesk) detects a ticket that breaches SLA. The integration workflow creates a Jira Task in the SUPPORT project with customer details, ticket ID, and breach timestamp so engineering can triage the escalation immediately.
• Compliance change tracking: Every infrastructure change request submitted via a web form auto-creates a Jira Task in the CHANGE project with the requester, affected systems, planned window, and business justification. Satisfies SOC 2 and ISO 27001 change management controls.
• Sprint story intake: A product backlog refinement tool exports approved stories. A scheduled BizFirst workflow reads the export and batch-creates Story issues in the upcoming sprint project so the backlog is populated before the planning meeting.
• DevOps incident logging: When a Kubernetes pod enters a CrashLoopBackOff state, a cluster monitoring webhook creates a Jira incident with namespace, pod name, recent logs, and a direct link to Grafana — giving SREs full context in the issue without manual copy-paste.

Configuration

Connection

Operation Fields

Sample Configuration

Create a Bug from a Datadog monitoring alert:

{
  "resource": "issue",
  "operation": "create",
  "Host": "https://acmecorp.atlassian.net",
  "Email": "automation@acmecorp.com",
  "ApiToken": "{{ $credentials.jiraApiToken }}",
  "ProjectKey": "OPS",
  "IssueType": "Bug",
  "Summary": "[P1 ALERT] {{ $json.alert.title }} — {{ $json.alert.source }}",
  "Description": "## Alert Details\n\n**Alert:** {{ $json.alert.title }}\n**Service:** {{ $json.alert.service }}\n**Environment:** {{ $json.alert.env }}\n**Triggered At:** {{ $json.alert.triggeredAt }}\n\n## Error\n\n```\n{{ $json.alert.message }}\n```\n\n**Runbook:** {{ $json.alert.runbookUrl }}",
  "Priority": "Highest",
  "Assignee": "oncall@acmecorp.com",
  "Labels": ["production", "alert", "datadog", "{{ $json.alert.service }}"],
  "CustomFields": {
    "customfield_10014": "OPS-EPIC-42",
    "customfield_10020": { "id": "{{ $json.sprint.id }}" }
  }
}

Validation Errors

Output Fields

Sample Output

{
  "status": "success",
  "issueId": "10482",
  "issueKey": "OPS-347",
  "self": "https://acmecorp.atlassian.net/rest/api/3/issue/10482",
  "resource": "issue",
  "operation": "create"
}

Expression Reference

Node Policies & GuardRails

• API token in Credentials Manager: Never embed ApiToken directly in node configuration. Reference it as {{ $credentials.jiraApiToken }}. Rotate tokens via Credentials Manager without touching workflow definitions.
• Dedup check before creation: For webhook-driven issue creation, always run issue/getAll with a JQL dedup query first (e.g. project = OPS AND summary ~ "{{ $json.alert.title }}" AND created >= -1h). Only create the issue if no existing match is found. This prevents duplicate issues from alert flapping or retried webhook deliveries.
• Rate limit awareness: Jira Cloud limits to approximately 50 requests per 10 seconds per user. If your workflow creates many issues in a loop, insert a Delay node between batches or use a queue pattern.
• Service account principle of least privilege: Use a dedicated Jira service account with only Create Issue permissions on the required projects. Do not use a personal account — token revocation on employee offboarding will break automation.
• Custom field documentation: Document the custom field IDs used in your workflows alongside the workflow definition. Field IDs are instance-specific and cannot be inferred from field names alone.

Workflow Examples

Example 1 — Create Jira Bug from Datadog Alert

Datadog webhook fires on a P1 alert → BizFirst workflow creates the Jira issue → posts Slack notification with issue key.

// Step 1: WebhookTrigger receives Datadog alert payload
// Step 2: issue/create
{
  "resource": "issue",
  "operation": "create",
  "ProjectKey": "OPS",
  "IssueType": "Bug",
  "Summary": "[P1] {{ $json.alert.title }}",
  "Description": "Service: {{ $json.alert.service }}\nEnv: production\n\n{{ $json.alert.message }}",
  "Priority": "Highest",
  "Assignee": "{{ $json.oncallEngineer }}",
  "Labels": ["p1", "production", "auto-created"]
}

// Step 3: Slack/postMessage
{
  "channel": "#incidents",
  "text": ":red_circle: P1 Bug created: *{{ $output.createIssue.issueKey }}* — {{ $json.alert.title }}\nhttps://acmecorp.atlassian.net/browse/{{ $output.createIssue.issueKey }}"
}

Example 2 — Create Story from Approved Backlog Item

Product tool webhook sends approved backlog item → BizFirst creates Story → assigns to team.

{
  "resource": "issue",
  "operation": "create",
  "ProjectKey": "PROD",
  "IssueType": "Story",
  "Summary": "{{ $json.item.title }}",
  "Description": "**Acceptance Criteria:**\n{{ $json.item.acceptanceCriteria }}\n\n**Business Value:** {{ $json.item.businessValue }}\n**Story Points:** {{ $json.item.storyPoints }}",
  "Priority": "Medium",
  "Labels": ["{{ $json.item.epic }}", "sprint-{{ $json.sprintNumber }}"],
  "CustomFields": {
    "customfield_10016": {{ $json.item.storyPoints }}
  }
}

Example 3 — Compliance Change Request from Web Form

Change request form submission → creates Jira Task with full audit fields → notifies change advisory board.

{
  "resource": "issue",
  "operation": "create",
  "ProjectKey": "CHANGE",
  "IssueType": "Task",
  "Summary": "Change Request: {{ $json.form.systemName }} — {{ $json.form.changeType }}",
  "Description": "**Requester:** {{ $json.form.requesterEmail }}\n**System:** {{ $json.form.systemName }}\n**Change Type:** {{ $json.form.changeType }}\n**Planned Window:** {{ $json.form.plannedStart }} to {{ $json.form.plannedEnd }}\n**Justification:** {{ $json.form.justification }}\n**Rollback Plan:** {{ $json.form.rollbackPlan }}",
  "Priority": "Medium",
  "Labels": ["change-request", "{{ $json.form.environment }}", "{{ $json.form.riskLevel }}"]
}