Skip to content

Update IncidentApp Jira documentation #24491

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
neko-dd merged 4 commits into from
Aug 7, 2024
Merged

Update IncidentApp Jira documentation #24491

Changes from all commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
f9ded27
Update jira.md
codhah92 Aug 6, 2024
ba69749
Remove "will" from verbiage
codhah92 Aug 6, 2024
c62ff06
Merge branch 'master' into cody-hahn/update-public-jira-docs
codhah92 Aug 7, 2024
41dc51a
Merge branch 'master' into cody-hahn/update-public-jira-docs
neko-dd Aug 7, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 7 additions & 4 deletions content/en/service_management/incident_management/guides/jira.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -27,13 +27,15 @@ To use automatic ticket creation, install the integration through the [Jira Inte

## Setup

1. On the [Integration Settings page][3], find the Jira integration.
1. Click the toggle for **Automatically create a Jira Issue**.
3. Define a template with dynamic variables to drive the content of the Jira ticket. The template maps severities to Jira priorities, adds labels, defines a dynamic assignee, and more.
1. On the [Integration Settings page][3], find the Jira integration.
2. Click the toggle for **Automatically create a Jira Issue**.
3. Add a condition to define when to automatically create a Jira issue. If this condition is left blank, the Jira issue is created when the incident is created.
4. Define a template with dynamic variables to drive the content of the Jira ticket. The template maps severities to Jira priorities, adds labels, defines a dynamic assignee, and more. Dynamic variables only work for **string** [Jira field types][5].

{{< img src="service_management/incidents/guide/jira/incident_jira_template.png" alt="Example template for Jira tickets that are automatically created from Datadog incidents" style="width:80%;" >}}

As incidents are created, an issue is also created in the corresponding Jira instance. This Jira issue links to the incident in Datadog for reference.
As incidents are created, an issue is also created in the corresponding Jira instance. This Jira issue links to the incident in Datadog for reference.
The Jira issue is unidirectionally synced with the incident based on the template defined in the [Integration Settings page][3].

## Further Reading

Expand All @@ -43,3 +45,4 @@ As incidents are created, an issue is also created in the corresponding Jira ins
[2]: /integrations/jira/
[3]: https://app.datadoghq.com/incidents/settings#Integrations
[4]: https://app.datadoghq.com/incidents
[5]: https://developer.atlassian.com/platform/forge/manifest-reference/modules/jira-custom-field-type