Integration Service Activities

Last updated Feb 19, 2026

Create Issue

Project compatibility

Windows | Cross-platform

Overview

Create a new issue in Jira Cloud using a selected project, issue type, and dynamic fields resolved from Jira configuration.

Description	API Method	API Path	Scopes
Create a Jira issue	POST	`/rest/api/2/issue`	`read:jira-work` - to resolve fields and project/issue-type metadata `write:jira-work` - to create issues via `POST /rest/api/2/issue` `read:jira-user` – recommended to resolve users for assignment

Input

Parameter	Description	Data Type
Project	Select the project or enter the project key/name; mapped to `fields.project.key`	string
Issue type	Select the issue type (for example, Epic, Story, Task, Bug); mapped to `fields.issuetype`	string
Dynamic fields	Additional fields enabled based on Project and Issue type; mapped to `fields.*`	varies

Output

Parameter	Description	Data Type
Issue	The created issue object returned by Jira	object
Issue ID	The numeric ID of the created issue	string
Issue key	The key of the created issue (for example `ABC-123`)	string

In API workflows, a single response object is returned as the output. Any required fields can be extracted directly from this object.
In RPA workflows, some output parameters may differ, but the necessary values can still be retrieved from the response object even if they are not explicitly exposed.

How it works

Note: The authenticated Jira account must have sufficient permissions to the respective resource in each action. See Jira project permissions documentation.

The Create Issue activity creates an issue in Jira based on the specified Project and Issue type, and dynamic standard and custom fields are retrieved from the combination of both.

Once you set the Project and Issue type fields, you can replace the Project and Issue type dynamically, with the help of variables, so that the fields remain on your canvas. In this case, you can only add the issue to a project where all the fields (or a subset of all the dynamic fields) apply.

Note: Select the Project and the related Issue type to dynamically retrieve additional input properties. Once the input properties are set, you can use variables for the Project and Issue type fields. When using variables, you can still use the same input properties when creating issues in different projects, as long as the properties still apply. Alternatively, create a sample Jira project with an issue type that includes all possible fields across various projects and issue types. This enables you to handle different fields in different projects when creating the issue.

Since issues can have different fields in different projects, we recommend creating a sample Project with an Issue type that contains all possible issue fields across multiple projects and issue types. This ensures that you can create issues across multiple projects and issue types.

Alternatively, when dynamically creating a Jira issue, you can use the Insert Record activity with an Issues object. However, this scenario prevents us from generating your issue input fields during design time and you must work with standard fields like Summary, Description, Assignee, etc.

For additional information and troubleshooting, see the Frequently Asked Questions section in Working with Jira activities.

On this page