Skip to content

jira issue create

  • Usage: jira issue create [flags]

Create a Jira issue from convenience flags, profile defaults, or a JSON payload. Use flags for common fields, --markdown for a Markdown description, and --json-input for full Jira field objects, custom fields, or rich ADF descriptions.

Create requests run through the validate-and-encode mutation pipeline before submission. --dry-run performs local parsing, alias normalisation, ADF validation, and preview rendering without resolving credentials or contacting Jira.

Headless --no-input needs complete input from flags, JSON, or profile defaults: project, issue type, and summary must all be known before the command can submit.

Fields

--assignee <USER>

Assign on creation: me, an email, or a Jira account ID

Allowed values:

  • me — current user

--label <NAME>…

Label to attach (repeatable)

--parent <KEY>

Parent issue key (for a subtask or epic child)

--priority <NAME>

Priority name

--project <KEY>

Project key (overrides the profile default)

--summary <TEXT>

Issue summary

--type <NAME>

Issue type name (overrides the profile default)

Input

--json-input <FILE>

Read issue create payload from JSON file (canonical for agents)

Accepts a file.

--markdown <MARKDOWN>

Issue description as Markdown (lossy convenience layer, converted to ADF)

--markdown-file <FILE>

Read the Markdown body from a file; - reads stdin

Accepts a file.

Safety

--dry-run

Preview mutation without submitting

Validation

--validate-remote

With --dry-run, validate against the live create screen (read-only createmeta fetch)

--verify

After a live create, re-fetch the issue and warn about requested fields the server did not apply

Output fields

With --output json, the response envelope's data object carries these fields. Run jira agent schema for the full machine-readable schema.

Field Type Description
dry_run boolean
issue.comments[] object Fields: author, body, created, id, self, updateAuthor, …
issue.editmeta object Fields: fields
issue.fields object Fields: assignee, comment, components, created, description, fixVersions, …
issue.id string
issue.key string
issue.linked_issues[] object
issue.self string
issue.subtasks[] object
issue.transitions[] object Fields: hasScreen, id, name
issue.worklogs[] object Fields: comment, id, started, timeSpentSeconds
preview object | null The validated payload submitted by a live write or proposed by a dry-run.
validated_remotely boolean Whether Jira metadata was used to validate the payload.
verification The optional post-write verification result requested with --verify.

Examples

jira issue create --project PROJ --type Task --summary "Fix the build"
jira issue create --project PROJ --type Bug --summary "Crash on startup" --assignee me --label regression # (1)!
jira issue create --project PROJ --type Task --summary "Draft" --dry-run # (2)!
jira issue create --project PROJ --type Task --summary "Fix" --markdown "## Steps\n\n1. Repro" # (3)!
jira issue create --json-input issue-create.json --dry-run --output=json # (4)!
  1. Create a bug assigned to you with a label
  2. Preview the create payload without contacting Jira
  3. Create with a Markdown description (converted to ADF client-side)
  4. Preview a full JSON payload for an agent