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 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.

Screenshots in this page use Jira as an example. The steps are identical for all issue management integrations - only the integration-specific fields differ. For Linear, the target container is labeled Team instead of Project.

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.

Mandatory fields in the policy configuration will be marked with an asterisk. These fields must be mapped before saving the policy.

Automated rule routing high-severity findings to a specific project

1. Scroll down and click Test Issue Creation to validate the configuration.

2. A dialog opens. Click Run Test.

Click Run Test to validate

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

Successful test confirms the configuration is working

1. Click Save to activate the rule.

Product-mapped configuration

Step 1 - Configure issue management on the Arnica product

1. Go to 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.

Configure the mapping at the product level

1. Scroll down and click Test Issue Creation to validate the configuration.

2. A dialog opens. Click Run Test.

Click Run Test to validate

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

Successful test confirms the configuration is working

1. Click Save.

Test and save from the bottom of the Issue Management tab

Each product can have at most one issue rule.

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.

The policy action references the product-level configuration automatically