> ## Documentation Index
> Fetch the complete documentation index at: https://bloodhound.specterops.io/llms.txt
> Use this file to discover all available pages before exploring further.
# Use Jira with BloodHound Enterprise
> Learn how to review and manage Jira issues created from BloodHound Enterprise findings.
After you complete the [installation and configuration](/integrations/atlassian/jira/configure), the integration synchronizes BloodHound Enterprise findings into Jira every five minutes. This page explains how the synchronized issues are structured and how to work with them in Jira.
## Jira issue model
The integration creates one Jira issue or incident for each synchronized BloodHound Enterprise finding.
| Jira object | Purpose |
| ------------------------ | --------------------------------------------------------------------------------- |
| **Issue or incident** | Represents one BloodHound Enterprise finding |
| **Priority** | Reflects the zone-to-priority mapping that you configured |
| **Due date** | Uses the due-day rule for the mapped Jira priority |
| **Labels** | Adds zone and domain labels so you can filter and report on the findings |
| **Auto-closure comment** | Explains that the finding was remediated when Jira closes the issue automatically |
If you connect a Jira Service Management project, the integration uses the configured request type and incident workflow instead of a standard Jira Software issue type.
## Jira issue format
When the integration creates a Jira issue, it follows a specific format to ensure that all relevant information is included:
The issue summary includes the zone, domain, affected principal, and finding ID.
**Example**: \[Tier-Zero] CORP.LOCAL - Administrator (12345)
The issue description includes the finding title, Graph View link, finding description, impact details, context, and remediation guidance.
| Field | Contents |
| ------------------------ | ------------------------------------------------------------------------------------------------------------ |
| **Finding Title** | The name of the attack path finding, such as *GenericWrite Privileges on Tier Zero Objects* |
| **BHE Link** | A direct link to the finding in the BloodHound Enterprise graph view |
| **Description** | An explanation of what the privilege allows and why it is a concern |
| **Impact** | The number of affected assets and exposure paths |
| **Context** | The severity level, finding type, environment details, and finding IDs |
| **Affected Entities** | Details about the source and target principals involved, including name, type, domain, object ID, and status |
| **Relationship** | Information about the relationship, including whether it is ACL-based and inherited |
| **Status** | Whether the finding is accepted plus its creation and update timestamps |
| **Remediation Guidance** | Both the quick fix and the detailed, step-by-step remediation steps |
Labels include zone and domain identifiers, which allow you to filter and report on the findings in Jira.
* **Example (zone)**: tier-zero, tier-one, hygiene
* **Example (domain)**: corp-local
The dates include the start date, which Jira sets when it creates the issue, and the due date, which the integration calculates from the configured priority mapping.
**Example**:
* Start date: Jun 20, 2026
* Due date: Jun 23, 2026
The priority reflects the zone-to-priority mapping in the integration's configuration settings.
**Example**: Highest
## Synchronization behavior
The integration keeps Jira aligned with BloodHound Enterprise automatically:
* It runs synchronization every five minutes
* It creates issues for new findings and updates existing issues when finding details change
* It avoids duplicates by tracking synchronization metadata on the Jira issues
* It runs a cleanup scheduler hourly and closes orphaned issues when **Auto-closure** is enabled and the cleanup interval is met
No action is required for automatic synchronization. The integration will automatically create and update Jira issues based on the configured settings.
If you need to manually trigger a synchronization, you can do so from the integration's [configuration settings](/integrations/atlassian/jira/configure#configure-synchronization-settings) in Jira.
## Review synchronized findings
Reviewing the synchronized findings in Jira allows you to triage and manage security issues identified by BloodHound Enterprise.
Use the synchronized issues the same way you manage other operational work in Jira:
* Filter by labels, priority, or due date to focus on the findings you want to triage first.
* Assign findings to the team that owns remediation
* Update workflow state as triage and remediation progress
* Add comments or work notes that document investigation and closure decisions
* Use the Graph View link to move from Jira back to the BloodHound Enterprise finding when you need more context