Skip to main content
Applies to BloodHound Enterprise only Use this page to troubleshoot common issues with the BloodHound Enterprise Jira integration. Start with the connection test, then validate the project configuration and synchronization scope.

​
Test Connection fails

If Test Connection fails, the most common causes are:
  • The Domain, Token ID, or Token Key value is incorrect
  • The BloodHound Enterprise token is expired or revoked
  • The BloodHound Enterprise URL does not include https://
  • Jira Cloud cannot reach the BloodHound Enterprise tenant
To resolve the issue:
  1. Verify the Domain, Token ID, and Token Key values in the Connection Settings tab.
  2. Confirm that the API token is still active in BloodHound Enterprise.
  3. Generate a new token if the current token is invalid or compromised.
  4. Confirm that the BloodHound Enterprise tenant is reachable from the internet.

​
Configuration tab is unavailable

The Configuration tab stays unavailable until the connection test succeeds. To unlock the configuration options:
  1. Re-enter the Jira connection values.
  2. Run Test Connection again.
  3. Wait for Jira to confirm that it retrieved the available BloodHound Enterprise domains.

​
Jira does not create issues

If the integration does not create issues after a synchronization, check the following:
  • At least one BHE Domain is selected
  • At least one BHE Zone is selected
  • BloodHound Enterprise currently has active findings in the selected domains and zones
  • The issues were not already created by an earlier synchronization
To verify the configuration:
  1. Open the Configuration tab.
  2. Confirm the selected domains and zones.
  3. Click Run Sync Now.
  4. Check the target Jira project again after the synchronization starts.

​
Jira uses the wrong priority or due date

The integration applies the priority and due date values from your configured mappings. To correct the issue:
  1. Review the Priority Mapping values for each BloodHound Enterprise zone.
  2. Review the Due Days values for the Jira priorities that the integration assigns.
  3. Save the updated configuration.
  4. Run a manual synchronization to apply the new mapping to future updates and new issues.

​
Auto-closure does not close remediated issues

If remediated findings do not close in Jira, the most common causes are:
  • Enable Auto-Closure is disabled
  • The configured cleanup interval has not elapsed yet
  • The Jira workflow does not provide a transition to Done
  • The integration has not completed a recent synchronization for the configured scope
To resolve the issue:
  1. Confirm that Enable Auto-Closure is enabled.
  2. Review the configured Cleanup Interval.
  3. Confirm that the Jira project workflow supports the transition to Done.
  4. Run a manual synchronization, then wait for the hourly cleanup scheduler to evaluate orphaned issues.

​
Jira Service Management request types do not appear

If the request type selector is empty in Jira Service Management:
  1. Confirm that the target project is a Jira Service Management project.
  2. Confirm that the project has incident request types available.
  3. Refresh the configuration page and rerun Test Connection if needed.

​
Common configuration messages

The following error messages may appear in the configuration screen when performing actions: