# Create Issue

> `UiPath.Jira.Activities.CreateIssue`

`UiPath.Jira.Activities.CreateIssue`

The **Create Issue** activity uses the [Jira API](https://bitbucket.org/farmas/atlassian.net-sdk/src/e2082af34475bd126f466ecd582501e090febc5e/docs/how-to-use-the-sdk.md) to create a new issue (**Issue**).

The activity outputs an issue object (**Issue**) that can be used as an input variable in subsequent activities (e.g., **Issue** in [Update Issue](https://docs.uipath.com/activities/other/latest/legacy-integrations/jira-update-issue)]).

## How it works

The following steps are an example of how the activity works from design time (i.e., the activity dependencies and input/output properties) to run time.

1. Complete the [Setup](https://docs.uipath.com/activities/other/latest/legacy-integrations/jira-setup) steps.
2. Add the [Jira Scope](https://docs.uipath.com/activities/other/latest/legacy-integrations/jira-scope) activity to your project.
3. Add the **Create Issue** activity inside the **Jira Scope** activity.
4. Create and enter a `String` and a `Project Key` variable for the Input properties.
5. Create and enter a `String` and a `Summary` variable for the Input properties.
6. Create and enter a `String` and a `Type` variable for the Input properties.
7. Create and enter a `Issue` and an `Issue` variable for the Output properties.

## Properties

The values for the following properties are specified when adding this activity to your project in UiPath Studio.

:::note
You can set custom fields by using either the (**Additional Fields**) or the (**Custom Fields**) property. They are provided to allow the RPA developer a choice of input parameters that they feel easiest to work with.
:::

### Common

* **Continue On Error** - This field only supports boolean values (True, False). The default value in this field is False. As a result, if this field is blank and an error is thrown, the execution of the project stops. If the value is set to True, the execution of the project continues regardless of any error.
* **DisplayName** - The display name of the activity. This field supports only strings or `String` variables.

### Input

* **Project Key** - The project key for the issue. This field supports only strings or `String` variables.
* **Summary** - The summary of a the issue. This field supports only strings or `String` variables.
* **Type** - The type of issue. This field supports only strings or `String` variables. (e.g. "Story")

### Misc

* **Private** - If selected, the values of variables and arguments are no longer logged at Verbose level.

### Output

* **Issue** - The newly created issue. Enter an `Issue` or `Issue` variable.

### Options

* **Additional Fields** - A dictionary containing key-value pairs for Jira fields. This property can be used with or instead of Custom Fields. A `String` field key and an `Object` value.
  + **Example**: a field name of "customfield_10007" and a value of "PRJ-1234". Some field names are case sensitive, e.g. "labels" instead of "Labels".
* **Custom Fields** - A dictionary containing key-value pairs for Jira fields. This property can be used with or instead of Additional Fields. Enter a `Dictionary<string,string>` or `Dictionary<string,string>` variable.
  + **Example**: New Dictionary(Of String, String) From {{"Epic Link", "PRJ-421" }}
* **Components** - The components you want associated with this issue. This field supports only `Strings` or `String` variables.
* **Description** - A string containing the description for the new issue. This field supports only `Strings` or `String` variables.
* **Parent Issue Key** - The key of the parent issue or epic. This field supports only `Strings` or `String` variables.
  :::note
  Currently using custom field names such as "Epic Link" is not supported With Additional Fields. You will need to use the custom field ID, such as "customfield_10007". The work-around is to use the Custom Fields property.
  :::