Jira - Create Issue

↩ Part of the Jira integration.

Description

Creates an issue in a Jira Cloud project (POST /issue). You give it the project key, a summary and, optionally, a description and any extra fields the project’s screen requires.

The description is written as plain text and the node converts it to Atlassian Document Format (ADF) before sending it — required by the API v3.

Configuration

Field	Type	Required	Description
`credentials_id`	credentials	Yes	Jira credential
`project_key`	text	Yes	Project key (e.g. `OPS`)
`issue_type`	text	No	Issue type (`Task`, `Bug`, `Story`…). Defaults to `Task`
`summary`	text	Yes	Issue summary (title)
`description`	textarea	No	Description in plain text; converted to ADF
`extra_fields`	json	No	Extra fields merged into `fields`, e.g. `{"priority":{"name":"High"}}`

project_key, summary and description accept dynamic variables. extra_fields does not — it is parsed as JSON as-is (if it is not valid JSON it is silently ignored).

Credentials

This module requires a Jira (Atlassian) credential:

Field	Description
`base_url`	Site URL, e.g. `https://your-domain.atlassian.net`
`email`	Atlassian account email
`api_token`	API token from id.atlassian.com

Output

data is the object Jira returns for a created issue:

{
  "id": "10042",
  "key": "OPS-123",
  "self": "https://your-domain.atlassian.net/rest/api/3/issue/10042"
}

Along with it, _meta:

{ "moduleVersion": "1.0.0", "success": true, "key": "OPS-123", "id": "10042", "totalMs": 412 }

Usage Example

Simple task

{
  "credentials_id": "jira_ops",
  "project_key": "OPS",
  "issue_type": "Task",
  "summary": "Review the monthly invoicing report"
}

Bug fed from a form

{
  "credentials_id": "jira_ops",
  "project_key": "OPS",
  "issue_type": "Bug",
  "summary": "{{data.subject}}",
  "description": "Reported by {{data.email}}\n\n{{data.details}}"
}

With priority and labels

{
  "credentials_id": "jira_ops",
  "project_key": "OPS",
  "issue_type": "Bug",
  "summary": "Checkout returns 500",
  "description": "Reproducible on the payment step.",
  "extra_fields": { "priority": { "name": "High" }, "labels": ["checkout", "urgent"] }
}

Notes

If issue_type is empty, Task is used.
Line breaks in description become separate ADF paragraphs.
Field names inside extra_fields must match your Jira instance (custom fields use ids such as customfield_10011).
A 400 usually means a field required by the project’s create screen is missing, or the issue type does not exist in that project. These errors are not retried — fix the data and run again.

Jira: Get issue — read the issue you just created.
Jira: Add comment — add context to the issue.
Jira: Transition issue — move it to another status.