> For the complete documentation index, see [llms.txt](https://docs.arnica.io/arnica-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.arnica.io/arnica-documentation/getting-started/ticket-management/creating-issues/automated-issue-creation.md).

# Automated Issue Creation

Automated issue creation uses policy rules to create issues without any user action, triggered by detecting a new finding. There are two approaches depending on how you want to manage the configuration.

**Static** - configuration (project, issue type, field mapping, etc.) is defined directly in the policy rule. Each rule targets a different project, with a different configuration.

**Product-mapped** - configuration is defined at the Arnica [product](https://app.arnica.io/#/inventory/products) level. Any policy using the `Create Issues (Product Mapped)` action automatically inherits the configuration from whichever product owns the finding. Best for dynamic, multi-team environments.

{% hint style="info" %}
Screenshots in this page use Jira as an example. The steps are identical for all issue management integrations - only the integration-specific fields differ.
{% endhint %}

## Static configuration

1. Go to **Admin - Policies** and expand **Code Risks** or **Secrets**, depending on the type of policy you want to create.
2. Create a new rule, or expand an existing rule.
3. Add a trigger and conditions (e.g. severity High or above, a specific repository, product, etc.).
4. Select the action **Create Issue (Specific)** and configure the integration, project, issue type, status mapping, and field mapping.

{% hint style="warning" %}
Mandatory fields in the policy configuration will be marked with an asterisk. These fields must be mapped before saving the policy.
{% endhint %}

<figure><img src="/files/aoqOU4IU9pU6q2PPAc9r" alt=""><figcaption><p>Automated rule routing high-severity findings to a specific project</p></figcaption></figure>

5. Scroll down and click **Test Issue Creation** to validate the configuration.
6. A dialog opens. Click **Run Test**.

<figure><img src="/files/u4gOY7iRU7q9VzltOren" alt=""><figcaption><p>Click Run Test to validate</p></figcaption></figure>

7. If successful, you'll see **Test completed successfully!** - click **Close**.

<figure><img src="/files/I1yBjc2js8RPwHxniDwl" alt=""><figcaption><p>Successful test confirms the configuration is working</p></figcaption></figure>

8. Click **Save** to activate the rule.

## Product-mapped configuration

### Step 1 - Configure issue management on the Arnica product

1. Go to **Inventory -** [**Products**](https://app.arnica.io/#/inventory/products) and select the required product.
2. Click the **Issue Management** tab.
3. Select the integration, project, issue type, and status mapping.
4. Optionally configure field mapping and a custom footer.

<figure><img src="/files/H1wdYGp2U9UJDcvZZ5QF" alt=""><figcaption><p>Configure the mapping at the product level</p></figcaption></figure>

5. Scroll down and click **Test Issue Creation** to validate the configuration.
6. A dialog opens. Click **Run Test**.

<figure><img src="/files/u4gOY7iRU7q9VzltOren" alt=""><figcaption><p>Click Run Test to validate</p></figcaption></figure>

7. If successful, you'll see **Test completed successfully!** - click **Close**.

<figure><img src="/files/I1yBjc2js8RPwHxniDwl" alt=""><figcaption><p>Successful test confirms the configuration is working</p></figcaption></figure>

8. Click **Save**.

<figure><img src="/files/D82oGkCGH6DbTWFEUc7R" alt=""><figcaption><p>Test and save from the bottom of the Issue Management tab</p></figcaption></figure>

{% hint style="info" %}
Each product can have at most one issue rule.
{% endhint %}

### Step 2 - Add the policy action

1. Go to **Admin - Policies** and expand **Code Risks** or **Secrets**, depending on the type of policy you want to create.
2. Create a new rule, or expand an existing rule.
3. Add or modify the **Create Issues (Product Mapped)** action. No configuration is needed here - the policy will automatically use the Issue Management configuration from whichever product owns the finding.
4. Click **Save**.

<figure><img src="/files/9srHsk5h8STIaqjPlXRV" alt=""><figcaption><p>The policy action references the product-level configuration automatically</p></figcaption></figure>