- 필수 기능
- 시작하기
- Glossary
- 표준 속성
- Guides
- Agent
- 통합
- 개방형텔레메트리
- 개발자
- Administrator's Guide
- API
- Datadog Mobile App
- CoScreen
- Cloudcraft
- 앱 내
- 서비스 관리
- 인프라스트럭처
- 애플리케이션 성능
- APM
- Continuous Profiler
- 스팬 시각화
- 데이터 스트림 모니터링
- 데이터 작업 모니터링
- 디지털 경험
- 소프트웨어 제공
- 보안
- AI Observability
- 로그 관리
- 관리
",t};e.buildCustomizationMenuUi=t;function n(e){let t='
",t}function s(e){let n=e.filter.currentValue||e.filter.defaultValue,t='${e.filter.label}
`,e.filter.options.forEach(s=>{let o=s.id===n;t+=``}),t+="${e.filter.label}
`,t+=`This feature is in Preview. Contact your Customer Success Manager to get access.
Request AccessDatadog Security supports ticketing management using Datadog Case Management and third-party integrations, such as Jira.
Datadog Case Management is available for all security products.
Notes:
Case management is supported for all security products that use signals:
Open any signal in these products and use the Create Case button to create a case in Datadog.
This sections describe how to use your Datadog Jira integration to sync tickets between Datadog Case Management and Jira bidirectionally.
Bidirectionally synchronization enables you to update Jira tickets automatically when changes occur in Datadog, and update some Datadog information when changes occur in Jira.
Birdirectional Datadog Case Management integration with Jira is supported for the following Code Security vulnerability categories:
Birdirectional Case Management integration with Jira enables you to sync Jira tickets with Datadog cases, but Datadog is the single source of truth for issue resolution.
A Datadog finding’s related Jira ticket can be closed manually, but a Datadog finding remains open if Datadog cannot confirm that the issue is fixed. This restriction ensures that a finding is not closed and removed from the list of signals when someone closes a related Jira ticket.
Closing a Datadog case without remediation does not close the finding either.
Remediation of the finding in Datadog or defining an exception by muting the finding are the only ways to close a finding. Once the finding is remediated, its related cases and Jira tickets are closed.
The following steps set up birdirectional case management integration with Jira and use Code Security vulnerabilites to verify that setup is successful.
You are ready to start creating bidirectional case management tickets.
If you do not see the Sync with Datadog (via Case Management) section, ensure that you have set up the prerequisites.
This procedure uses Code Security vulnerabilites to demonstrate how to create bidirectional case management tickets.
Notes:
Existing bidirectional Jira tickets are listed in a signal’s Ticketing or Next Steps sections.
Here’s an example from a Static Code (SAST) signal:
Hover over the Jira ticket to see its details.
Details such as assignee and status are provided along with a timeline of the Jira issue and Datadog case changes.
Closed Jira tickets are green.
In Datadog Associated Case, the related Datadog case is provided. Click the case name to open it in Case Management.
Deleting a case does not delete related Jira tickets, but deleting a case project deattaches all tickets from related signals.
There are several case management facets, including:
You can query attributes and create dashboards using these facets.