Add id=jira so we can use #jira anchor like we do for ServiceNow and Linear

[pedroh-reis]

What does this PR do? What is the motivation?

The URL:

• https://docs.datadoghq.com/incident_response/work_management/notifications_integrations/#linear
• https://docs.datadoghq.com/incident_response/work_management/notifications_integrations/#servicenow

works properly, but

• https://docs.datadoghq.com/incident_response/work_management/notifications_integrations/#jira

doesn't.

This PR adds id=jira to the Jira section, so the anchor can work for Jira too

Merge readiness

• Ready for merge

For Datadog employees:

• ⚠️ Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). If you've already created your PR with an incorrect branch name, please rename your branch and open a fresh PR.
• 🤖 New: Comment with /review to run an automated check that catches common issues before a Documentation team member reviews your PR.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/esther/docs-pr/work-management-jira-anchor/incident_response/work_management/notifications_integrations

[Copilot]

Pull request overview

Adds the missing #jira anchor to the Jira configuration section.

Changes:

• Added id="jira" to the Jira configuration component.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[OliviaShoup]

thanks for the PR! 🚀