[SEC-36494] Document Linear ticket creation rules - #39728
Merged
Conversation
Contributor
Preview links (active after the
|
brett0000FF
approved these changes
Sep 8, 2026
brett0000FF
left a comment
brett0000FF
left a comment
Collaborator
There was a problem hiding this comment.
Looks good! Note: Please fix the link references I noted in my comment before merging.
VivianeQian
force-pushed
the
viviane.qian/SEC-36494
branch
from
September 9, 2026 08:36
97d9c34 to
b7187de
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do? What is the motivation?
Documents Linear support for Security ticket creation rules. The setup instructions now use tabs for Jira, Linear, and Case Management, and list the required and optional Linear destination fields. This helps users route new security findings into their existing Linear workflow without creating issues manually.
Merge readiness
For Datadog employees:
<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./reviewto run an automated check that catches common issues before a Documentation team member reviews your PR.AI assistance
Used Codex to update the documentation, structure the integration tabs, and perform source-level validation.
Additional notes
Documentation-only change.
git diff --checkpassed, and the Hugo tab shortcode pairs are balanced.