Create Issue - Blink Documentation

Creates a new issue.

Basic Parameters

Parameter	Description
Assignee	The email address or the display name of the assignee. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com. Therefore, it’s recommended to use the user’s email to prevent the string from matching multiple values, which is ambiguous and will cause the action to fail.
Description	Description of the issue.
Issue Type	The type of the issue. The type must be defined in your Jira workspace.
Project Key Or ID	The project ID or project key (case sensitive).
Reporter	The email address or the display name of the reporter. The string can match the prefix of the attribute’s value. For example, query=john matches a user with a displayName of John Smith and a user with an emailAddress of johnson@example.com. Therefore, it’s recommended to use the user’s email to prevent the string from matching multiple values, which is ambiguous and will cause the action to fail.
Summary	Summary of the issue.

Parameter	Description
Components	A list of Components that need to be set up in the new issue. Example input: `[ { “id”: “10000” }, { “name”: “Component 1” } ]`
Custom Fields	Custom fields in JSON form, where the key is the name of the custom field mapped to it’s value. Example input: `{ “foobar”: 10, “incident_status”: “resolved” }` Will set the custom field named “foobar” to 10 and “incident_status” to “resolved”.
Labels	A comma separated list of labels for the issue.
Transition	Details of a transition. Required when performing a transition, optional when creating or editing an issue. Example input: `{ “id”: "<string>", “looped”: true }`

{
	"id": "10000",
	"key": "TST-24",
	"self": "http://www.example.com/jira/rest/api/2/issue/10000"
}

Preview this Workflow on desktop