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

# Issue Management Integrations

Arnica integrates with your existing issue tracking systems to automate the full lifecycle of security findings - from detection through fix validation and automatic ticket closure.

## Supported integrations

Arnica currently supports [Jira](/arnica-documentation/getting-started/ticket-management/jira-integration.md), [ADO Boards](/arnica-documentation/getting-started/ticket-management/ado-boards-integration.md), and [ServiceNow](/arnica-documentation/getting-started/ticket-management/servicenow.md) (coming soon).

## How Arnica manages the full issue lifecycle

Arnica doesn't just create issues - it manages the complete lifecycle from detection to closure, without requiring manual intervention from developers or security teams.

1. **Detect** - a finding is identified (e.g. a hardcoded secret pushed to a repo, a vulnerable dependency on a PR).
2. **Create** - a policy rule triggers and Arnica opens an issue in the configured project with the right fields and assignee.
3. **Fix** - the developer resolves the underlying issue (removes the vulnerable code, deletes or archives the affected repository, etc.).
4. **Validate** - Arnica automatically detects that the finding has been resolved.
5. **Close** - Arnica marks the finding as **Resolved Automatically** and transitions the linked ticket to the closed status defined in your status mapping.

Developers don't need to touch Arnica at all. The fix triggers the entire resolution chain automatically, saving significant triage and tracking overhead.

{% hint style="info" %}
Arnica is the source of truth for finding resolution. Closing a ticket manually in your issue tracker does not resolve the finding in Arnica - resolution flows from Arnica outward, not the other way around.
{% endhint %}

## Issue creation approaches

Once you have connected an integration, choose how you want issues to be created:

* [Manual Issue Creation](/arnica-documentation/getting-started/ticket-management/creating-issues/manual-issue-creation.md) - users create issues on demand from any finding
* [Automated Issue Creation](/arnica-documentation/getting-started/ticket-management/creating-issues/automated-issue-creation.md) - policy rules create and manage issues automatically


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.arnica.io/arnica-documentation/getting-started/ticket-management.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.