Manual Issue Creation

Manual issue creation lets any user create an issue in their connected issue tracker directly from a finding with a single click. The issue is created using the configuration defined in the matching policy rule.

Manual issue creation is not zero-config. A policy rule with the User Created Issue trigger must be set up first.

Screenshots in this page use Jira as an example. The steps are identical for all issue management integrations - only the integration-specific fields (workspace, project type, etc.) differ.

Step 1 - Configure the policy rule

1. Go to Admin - Policies and expand Code Risks or Secrets, depending on the type of policy you want to create.

2. Add a new rule with the trigger User Created Issue.

3. Set conditions as needed (e.g. Always TRUE to apply to all findings, or scope to a specific repository or severity).

4. Select the action Create Issue (Specific) and configure:

   • Issue Integration - select the connected workspace.

   • Project - the project where issues will be created.

   • Issue Type - e.g. Task, Bug, Story.

   • Open Status / Close Status - map statuses so Arnica can close the ticket when the finding is resolved.

   • Field Mapping - map fields to static values or dynamic finding properties (e.g. severity, repository, file path).

   • Custom Footer (optional) - text appended to every issue description.

Bonus Points - Instead of Create Issue (Specific), you can use Create Issues (Product Mapped) to dynamically route manual issues to the right project based on the product that owns the finding. This is ideal for multi-team environments where different teams use different projects. See Using product-mapped configuration for manual issues below, or reach out to your CSM for more information on product mapping.

Policy rule configured for manual issue creation

Step 2 - Test the configuration

1. Click Test Issue Creation at the bottom of the Create Issue action.

2. A dialog opens confirming the test process. Click Run Test.

Click Run Test to validate the configuration

1. If the configuration is valid, you'll see Test completed successfully! - click Close.

A successful test creates and auto-closes a test issue

1. Click Save to activate the rule.

Step 3 - Create an issue from a finding

1. Open any finding in Secrets or Code Risks.

2. Click the Create Issue button in the top-right corner of the finding panel.

Click Create Issue to trigger the policy

1. The issue link appears in the Issue column of the risk list.

The issue link appears in the Issue column

Using product-mapped configuration for manual issues

You can use Create Issues (Product Mapped) with the User Created Issue trigger so that manual issues are automatically routed to the right project based on the product that owns the finding - without hardcoding any Jira configuration in the policy rule itself.

Step 1 - Configure issue management at the product level (see Automated Issue Creation - Product-mapped configuration).

Step 2 - Create the policy rule:

1. Go to Admin - Policies and expand Code Risks or Secrets.

2. Add a new rule with the trigger User Created Issue.

3. Set conditions as needed.

4. Add the action Create Issues (Product Mapped). No project or field configuration is needed - it is inherited from the product.

5. Test and save the rule.

When a user clicks Create Issue on a finding, Arnica will use the Issue Management configuration from the product that owns the finding to create the issue in the right place automatically.