Create Issue

UiPath.Jira.IntegrationService.Activities.CreateIssue

Description

Creates an issue in Jira.

Project compatibility

Windows | Cross-platform

Configuration

• Connection - The connection established in Integration Service. Access the dropdown menu to choose, add, or manage connections. This field supports strings or String variables.
• Project - The project where you want to create a new issue. Start typing the project name or key to search the list of projects available in the dropdown menu. This field supports only strings or String variables.
• Issue type - The type of isse you wish to create (task, story, bug, epic, etc.). Select one to enable custom fields.

Note: Depending on the Project and Issue type you select, a list of additional properties is displayed, e.g., Summary, Description, Components, etc.

Output

• Issue ID - The ID of the created issue, stored in a String variable.
• Issue key - The key of the created issue, stored in a String variable.

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, Issue, and dynamic standard and custom fields fetched from the combination of both.

Once you set the Project and Issue fields, you can set the Project and Issue 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.

We recommend that you create a Sample Project with an Issue type that contains all possible issue fields across multiple projects and issue types, so that you can create issues across multiple projects and issue types. This is because issues can have different fields in different projects.

Alternatively, when dynamically creating a Jira issue, you can use the Insert Record activity with an Issues object. This scenario, however, 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.