finding_jira_issues

Creates, updates, deletes, gets or lists a finding_jira_issues resource.

Overview

Name	finding_jira_issues
Type	Resource
Id	datadog.security.finding_jira_issues

Fields

The following fields are returned by SELECT queries:

SELECT not supported for this resource, use SHOW METHODS to view available operations for the resource.

Methods

The following methods are available for this resource:

Name	Accessible by	Required Params	Optional Params	Description
create_jira_issues	insert	data		Create Jira issues for security findings.<br />This operation creates a case in Datadog and a Jira issue linked to that case for bidirectional sync between Datadog and Jira. To configure the Jira integration, see [Bidirectional ticket syncing with Jira](https:​//docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira). You can create up to 50 Jira issues per request and associate up to 50 security findings per Jira issue. Security findings that are already attached to another Jira issue will be detached from their previous Jira issue and attached to the newly created Jira issue.
attach_jira_issue	update			Attach security findings to a Jira issue by providing the Jira issue URL.<br />You can attach up to 50 security findings per Jira issue. If the Jira issue is not linked to any case, this operation will create a case for the security findings and link the Jira issue to the newly created case. To configure the Jira integration, see [Bidirectional ticket syncing with Jira](https:​//docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira). Security findings that are already attached to another Jira issue will be detached from their previous Jira issue and attached to the specified Jira issue.

Parameters

Parameters can be passed in the WHERE clause of a query. Check the Methods section to see which parameters are required or optional for each operation.

Name	Datatype	Description
site	string	The Datadog site (region) for your organization, for example datadoghq.com, us3.datadoghq.com, us5.datadoghq.com, ap1.datadoghq.com, ap2.datadoghq.com, datadoghq.eu, ddog-gov.com. Resolved from the DD_SITE environment variable when set. Optional: defaults to datadoghq.com, or the value of the DD_SITE environment variable when set; a WHERE value overrides both.

INSERT examples

create_jira_issues

Create Jira issues for security findings.<br />This operation creates a case in Datadog and a Jira issue linked to that case for bidirectional sync between Datadog and Jira. To configure the Jira integration, see [Bidirectional ticket syncing with Jira](https:​//docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira). You can create up to 50 Jira issues per request and associate up to 50 security findings per Jira issue. Security findings that are already attached to another Jira issue will be detached from their previous Jira issue and attached to the newly created Jira issue.

INSERT INTO datadog.security.finding_jira_issues (
data
)
SELECT 
'{{ data }}' /* required */
RETURNING
data
;

Manifest

# Description fields are for documentation purposes
- name: finding_jira_issues
props:
  - name: data
    description: |
      Array of Jira issue creation request data objects.
    value:
      - attributes:
          assignee_id: "{{ assignee_id }}"
          description: "{{ description }}"
          fields: "{{ fields }}"
          priority: "{{ priority }}"
          title: "{{ title }}"
        relationships:
          findings:
            data:
              - id: "{{ id }}"
                type: "{{ type }}"
          project:
            data:
              id: "{{ id }}"
              type: "{{ type }}"
        type: "{{ type }}"

UPDATE examples

attach_jira_issue

Attach security findings to a Jira issue by providing the Jira issue URL.<br />You can attach up to 50 security findings per Jira issue. If the Jira issue is not linked to any case, this operation will create a case for the security findings and link the Jira issue to the newly created case. To configure the Jira integration, see [Bidirectional ticket syncing with Jira](https:​//docs.datadoghq.com/security/ticketing_integrations/#bidirectional-ticket-syncing-with-jira). Security findings that are already attached to another Jira issue will be detached from their previous Jira issue and attached to the specified Jira issue.

UPDATE datadog.security.finding_jira_issues
SET 
data = '{{ data }}'
WHERE 
RETURNING
data;