• /
  • EnglishEspañolFrançais日本語한국어Português
  • Log inStart now

Create a Jira issue

Creates a new Jira issue.

For authentication setup, see Jira issue actions.

Input Field

Optionality

Type

Description

Example

authToken

Required

String

Base64-encoded string of email:API_Token for Basic Authentication. Must be provided as a secret. See Create and manage API tokens.

"${{ :secrets:jiraAuthToken }}"

domain

Required

String

Your Jira Cloud instance domain (company name). Used to construct the base URL your-domain.atlassian.net.

"mycompany"

projectKey

Required

String

The key of the Jira project in which to create the issue.

"PROJ"

summary

Required

String

A brief summary or title for the new issue.

"Fix bug in login page"

description

Required

String

A detailed description for the issue.

"Users are unable to log in."

issueTypeName

Required

String

The type of issue to create.

"Bug" or "Story"

parentKey

Optional

String

The key of the parent issue. Used to create subtasks or child issues.

"PROJ-123"

labels

Optional

List

A list of labels to apply to the issue.

["alerting", "p1"]

fields

Optional

Map

A map for all other issue fields not listed above, including priority, assignee, components, and custom fields. To get all fields with allowed values for an issue type, use GET /rest/api/3/issue/{issueKey}/editmeta. See the fields reference table below.

{"priority": {"name": "Highest"}, "assignee": {"accountId": "5e6b8c..."}}

selectors

Optional

List

A list of named expressions to extract specific values from the response.

[{"name": "summary", "expression": ".responseBody.result.summary"}]

Fields reference

Field

Type

Description

priority

Object

Issue priority. Example: {"name": "High"}

assignee

Object

User to assign the issue to. Example: {"accountId": "5e6b8c..."}

reporter

Object

User reporting the issue.

components

Array

Project components to associate with the issue. Example: [{"name": "Backend"}]

duedate

Date

Due date for the issue. Example: "2025-12-31"

fixVersions

Array

Fix version(s) for the issue.

environment

String

Description of the environment in which the issue occurred.

customfield_10016

Integer

Story point estimate.

customfield_10001

Team ID

Team associated with the issue.

customfield_10020

Array

Sprint association.

customfield_10022

Date

Target start date.

customfield_10023

Date

Target end date.

Output Field

Type

Example

response

Object

{
"id": "10001",
"key": "PROJ-124",
"self": "..."
}

success

Boolean

success: true | false

errorMessage

String

{
"errorMessages": [],
"errors": {
"project": "Project is required.",
"issuetype": "Issue type is required."
}
}

Workflow example

name: create_jira_issue_example
description: 'Creates a new bug ticket with priority and labels.'
steps:
- name: create_jira_issue
type: action
action: jira.issue.create
version: 1
inputs:
domain: new-relic
authToken: ${{ :secrets:jiraBasicAuth }}
projectKey: PROJ
summary: Main order flow broken
issueTypeName: Story
description: Order entry fails when selecting supplier.
labels:
- staging
- blitz_test
fields:
priority:
name: Highest
components:
- name: "Backend"
duedate: "2025-12-31"
next: end
Copyright © 2026 New Relic Inc.

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.