Automating Jira Ticketing

In addition to creating Jira tickets from OX, you can automate several aspects of how security issues are tracked and updated in Jira. These automations help you sync key information between platforms, reduce manual updates, and ensure consistency across issue workflows.

You can automatically add comments to Jira tickets based on actions taken in OX, set due dates aligned with your SLAs or custom rules, and map issue severity to Jira priorities. These capabilities improve collaboration between security and development teams by keeping Jira issues accurate and up to date.

Adding Comments to Jira Automatically

You can configure OX platform to automatically add comments to Jira tickets when specific actions are taken on OX issues. This ensures that developers working in Jira are informed of changes made by security teams without needing direct communication.

When enabled, OX adds the comment directly to the linked Jira ticket automatically, no manual entry is required.

You can choose which actions should trigger comments and enable them individually. This allows teams to control the level of detail shown in Jira and avoid unnecessary noise.

To add comments automatically:

1. Go to Settings > TICKETING AND MESSAGING.

2. Enable the options that you want, as follows:

• The issue is resolved: The issue was resolved or reopen in the OX platform.

• The issue's severity changes: The severity definition of this issue was changed.

• The issues is excluded: The issue was excluded from the security scan and from now on this issue will not be reported.

• The issue is no longer available: The issue was not identified in a specific scan.

• The issue is reported as false positive: The issue was manually defined in the OX platform as false positive, and a comment about it is automatically generated in the Jira ticket linked to this issue.

• A comment was added to the OX issue: A new comment is manually added to an issue in the OX platform, and the same comment is automatically added in the Jira ticket.

Mapping Default Due Dates

You can add to a Jira ticket a custom field named Due Date and then configure a default Due Date value in OX platform based on the OX issue severity. This helps ensure that tickets align with your SLA expectations without requiring manual date entry.

Jira ticket must include the Due Date field for this mapping to work. If you manually change the value of the Due Date parameter in Jira while creating the ticket, that value overrides the default defined in OX.

For example, if a critical issue has a 3-day SLA, the Due Date parameter in Jira will automatically be set to 3 days from the ticket creation date, unless manually overridden.

To map default Due Dates:

1. Go to Settings > TICKETING AND MESSAGING.

1. Enable Add Due Dates to Jira tickets.

2. Set the Due Date parameter in Jira in one of the following ways:

• Use Due Dates from OX SLA Settings: The Due Date is automatically taken from the Settings > SLA definitions in OX.

• Set default Due Dates: Define manually SLA for each severity level. These settings override all the other SLA settings for the selected issues.

Mapping Jira Priorities

You can map issue severity levels in OX to the Priority parameter values in Jira. This ensures that each ticket created reflects the appropriate level of urgency within your existing Jira workflows.

For example, mappings might include:

• Critical severity → Highest Jira priority

• High severity → High Jira priority

• Medium severity → Medium Jira priority

After you configure these settings, all the they are applied automatically for all the new when tickets created for OX issues.

To map priorities:

1. Go to Settings > TICKETING AND MESSAGING.

1. Enable Map severity to Jira Priority field.

2. Enable the severity levels that you want to map and define the Priority value in Jira associated with each severity level in OX.