Getting Started

Endpoints

Patch Management

Vulnerability Management

Software Deployment & IT Assets

Automation & Remote Desktop

Real-Time Reports & Alerts

Account Access & Management

SSO Authentication

Security Concerns

Need Help?

Action1 5 Documentation 5 Action1 Connector for Jira 5 Troubleshoot the Action1 Connector for Jira

Troubleshoot the Action1 Connector for Jira

Use this page to review common setup and sync issues for the Action1 Connector for Jira.

If the integration is not working as expected, first verify the Action1 connection, organization mapping, ticketing rules, and current sync status.

Start with these checks

Before looking at a specific symptom, verify the following:

  • The Action1 connection settings are correct.
  • The Client ID and Client Secret are valid.
  • The API credentials still have access to the required Action1 organizations.
  • The required minimum Action1 API role permissions are assigned.
  • The relevant signal is enabled in Rules.
  • At least one Action1 organization is mapped to a Jira space.
  • Sync has been run manually, or scheduled sync is enabled.

Problem: The app cannot connect to Action1

If the app cannot connect to Action1, verify the following:

  • The Action1 API URL or connection settings are correct.
  • The Client ID is correct.
  • The Client Secret is correct.
  • The API credentials are still active.
  • The API credentials have access to the required Action1 organizations.
  • The minimum required Action1 API role permissions are assigned:
    • View Endpoints
    • View Automations and History
    • View Vulnerabilities
    • View dashboards

If the problem persists, regenerate the credentials (if appropriate) and update the saved connection settings in Jira.

 

Problem: No Jira tickets were created

If sync ran but no Jira tickets were created, verify the following:

  • The relevant signal is enabled in Rules.
  • At least one Action1 organization is mapped to a Jira space.
  • The Action1 endpoint conditions actually match your configured rules.
  • Sync has completed or is still continuing in the background.

For example, no tickets may be created due to the following reasons:

  • No qualifying vulnerabilities match your selected criteria.
  • No endpoints currently require updates based on your settings.
  • No endpoints are offline long enough to match the configured threshold.
  • No relevant automation failures exist for the selected scope.

Problem: Tickets were created in the wrong Jira space

If tickets were created in an unexpected Jira space, review your organization mapping configuration.

Verify that:

  • The correct Action1 organization is mapped
  • The correct Jira space is selected for that organization
  • the mapping was saved successfully before sync was run

If needed, update the mapping and run sync again.

Problem: A signal is enabled, but a ticket does not appear

If a signal is enabled but no ticket appears, verify the following:

  • The signal is enabled in Rules.
  • The endpoint conditions in Action1 actually match the configured rules.
  • The Action1 organization is mapped to a Jira space.
  • Sync has run after the configuration was saved.
  • Sync is not still continuing in the background.

Not every enabled signal will always create tickets. A signal must still match the configured conditions and the endpoint state in Action1.

Problem: Sync is still running or continuing

For larger environments, sync may continue automatically in the background after the initial run starts.

This is expected behavior. If sync still shows a running or continuing state, review Sync Status again later to confirm whether processing has completed.

Problem: Sync shows Needs retry

If sync shows Needs retry, some work may not have completed successfully, and another attempt may be required.

Start by checking:

  • The Action1 connection
  • Organization mapping
  • Ticketing rules
  • Whether the latest run is still continuing
  • Whether the same issue appears repeatedly across multiple runs

If needed, run sync again after confirming the configuration.

Problem: Expected tickets were not updated

If expected Jira tickets were not created or updated as anticipated, verify the following:

  • The relevant Action1 signal still matches current conditions.
  • Sync was run after the latest configuration changes.
  • The organization mapping is correct.
  • The integration is still connected successfully to Action1.

If the condition no longer matches, the connector may not create new work for that endpoint.

Problem: Connection works, but sync results are not what you expected

If the connection succeeds but sync results are still unexpected, review:

  • Which signals are enabled
  • How your rule settings are configured
  • Whether the relevant Action1 organizations are mapped
  • Whether the environment currently contains qualifying endpoint conditions

In many cases, the issue is caused by configuration or scope rather than connectivity.

When to contact support

Contact support in the following situations:

  • The app cannot connect to Action1, even with confirmed valid credentials.
  • Expected Action1 organizations do not appear for mapping.
  • Sync repeatedly shows Needs retry.
  • Expected qualifying conditions never result in Jira tickets.
  • Tickets consistently route to unexpected Jira spaces after mapping has been reviewed.

See also: