Action1 Connector for Jira FAQ
General
Does this integration require Jira Cloud?
Yes. The integration is designed for Jira Cloud.
What does the integration do?
The integration helps IT and security teams bring important Action1 endpoint signals into Jira as tracked work items.
Depending on configuration, the connector can create and maintain Jira tickets for supported Action1 endpoint signals.
Which Action1 signals are supported?
The integration supports the following Action1 signal types:
- Vulnerabilities detected
- Updates required
- Reboot required
- Endpoint offline
- Automation failures detected
Do the API credentials need access to specific Action1 organizations?
Yes. The API credentials used by the integration must have permission to read the Action1 organizations you want to sync.
If the credentials do not have access to those organizations, they may not appear correctly for mapping or may not be processed during sync.
Do I need to map Action1 organizations before running sync?
Yes. At least one Action1 organization should be mapped to a Jira space before sync can create Jira tickets for that organization.
Jira behavior
What gets created in Jira?
The integration can create Jira tickets for qualifying Action1 endpoint conditions, based on your configuration.
Does the integration always create a new Jira ticket?
Not always. The connector is designed to create and maintain Jira tickets over time and may update existing tickets when appropriate.
Will the integration create duplicate Jira tickets?
The integration is designed to reduce unnecessary duplicate ticket creation and to maintain Jira tickets over time where appropriate.
Can different Action1 organizations route to different Jira spaces?
Yes. You can map different Action1 organizations to different Jira spaces.
Can I change the Jira space for an organization later?
Yes. You can update the organization mapping if you want an Action1 organization to route to a different Jira space.
Sync behavior
Can I run sync manually?
Yes. You can start sync manually from the Sync Status section.
Can I enable scheduled sync?
Yes. You can enable scheduled sync to keep Jira aligned with Action1 automatically.
Can sync continue automatically in the background?
Yes. For larger environments, sync may continue automatically in the background after the initial run starts.
Why does sync sometimes take longer than expected?
In larger environments, the integration may need additional background processing time to complete sync. This is expected behavior.
What does “Needs retry” mean?
If sync shows Needs retry, some work may not have completed successfully and another attempt may be required.
Rules and scope
Will every enabled signal always create a Jira ticket?
No. A signal must still match the configured conditions and current endpoint state in Action1.
Why were no Jira tickets created?
Possible reasons include:
- The relevant signal is not enabled
- No Action1 organization is mapped
- The current endpoint conditions do not match your configured rules
- Sync has not completed yet or is still continuing in the background
Why did a signal not create a Jira ticket for a specific endpoint?
A signal may be enabled, but the endpoint must still meet the configured conditions before a Jira ticket is created.