Skip to content

Commit 6c32770

Browse files
committed
more review comments
1 parent 747ed05 commit 6c32770

File tree

2 files changed

+6
-6
lines changed

2 files changed

+6
-6
lines changed

content/en/error_tracking/ticketing_systems/case_management.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -72,7 +72,7 @@ The relationship between cases and issues is a 1:N relationship. A single case c
7272

7373
## State dual-way sync between issues and cases
7474

75-
### Single Error Tracking issue linked to a Case Management case
75+
### Single Error Tracking issue linked to single Case Management case
7676

7777
When a single Error Tracking issue is linked to a Case Management case, their states are two-way synced. The issue state is mapped to
7878
the default status of the corresponding case status group:
@@ -85,7 +85,7 @@ the default status of the corresponding case status group:
8585
| IGNORED | Closed |
8686
| EXCLUDED | Closed |
8787

88-
### Multiple Error Tracking issues linked to the same Case Management case
88+
### Multiple Error Tracking issues linked to single Case Management case
8989

9090
When multiple Error Tracking issues are linked to the same Case Management case, there is also a sync between their states, depending on the situation:
9191
- If you update the status of the case, all linked issues are updated following the state mapping described in the previous paragraph.

content/en/error_tracking/ticketing_systems/jira.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -23,7 +23,7 @@ Integrate Jira with Error Tracking to create and link Jira tickets to Error Trac
2323
- Automatically route issues to specific Jira boards using automation rules
2424
- Automatically create Jira tickets for Error Tracking issues matching specific criteria.
2525

26-
## Setup
26+
## Prerequisites
2727

2828
Follow [these steps][7] to set up the Jira integration for Datadog.
2929

@@ -75,13 +75,13 @@ The relationship between tickets and issues is a 1:N relationship. A single tick
7575

7676
If two-way sync is enabled and configured between Datadog and Jira projects, the states of Error Tracking issues and Jira tickets are mirrored. If you encounter any unexpected behavior on this states sync, see the [Troubleshooting](#troubleshooting) section for how to fix your configuration.
7777

78-
### Single Error Tracking issue linked to a Jira ticket
78+
### Single Error Tracking issue linked to single Jira ticket
7979

8080
When a single Error Tracking issue is linked to a Jira ticket, their states are two-way synced. The mapping between these states can be configured in the Data Sync settings of the ticket creation or automation rule forms:
8181

8282
{{< img src="error_tracking/jira-status-mapping.png" alt="Map Error Tracking issue states to Jira ticket statuses" style="width:100%;" >}}
8383

84-
### Multiple Error Tracking issues linked to the same Jira ticket
84+
### Multiple Error Tracking issues linked to single Jira ticket
8585

8686
When multiple Error Tracking issues are linked to the same Jira ticket, there is also a sync between their states, depending on the situation. If you update the status of the ticket, all linked issues are updated to mirror this state according to your mapping.
8787

@@ -151,7 +151,7 @@ When a new Error Tracking issue is created, rules are evaluated and the first ru
151151

152152
## Troubleshooting
153153

154-
If you experience unexpected behavior with Error Tracking ticketing integrations, the troubleshooting steps below can help you resolve the issue quickly. If you continue to have trouble, reach out to [Datadog support][5].
154+
If you experience unexpected behaviors using ticketing systems with Error Tracking, the following troubleshooting steps can help you resolve the issue quickly. If you continue to have trouble, reach out to [Datadog support][5].
155155

156156
### Sync is broken between Jira and Error Tracking
157157

0 commit comments

Comments
 (0)