Skip to content

[DASh 2025] Ticketing Systems topic for Security Overview #29778

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.

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

Conversation

michaelcretzman
Copy link
Contributor

Doc ticket: DOCS-10841
Editing ticket: DOCS-11099

What does this PR do? What is the motivation?

  • new topic named Ticketing Systems for Security Overview
  • Bidirectional sync is the new functionality

Merge instructions

To be merged the day before DASH.

and adding product support markdown
DOCS-10841

- added new topic for bidirectional case management
@michaelcretzman michaelcretzman requested a review from a team as a code owner June 5, 2025 22:17
@github-actions github-actions bot added Architecture Everything related to the Doc backend Images Images are added/removed with this PR labels Jun 5, 2025
@michaelcretzman michaelcretzman requested a review from cswatt June 5, 2025 22:18
Copy link
Contributor

github-actions bot commented Jun 5, 2025

✅ Documentation Team Review

The documentation team has approved this pull request. Thank you for your contribution!

@michaelcretzman michaelcretzman self-assigned this Jun 5, 2025
@michaelcretzman michaelcretzman added editorial review Waiting on a more in-depth review okr11 labels Jun 5, 2025
Copy link
Contributor

github-actions bot commented Jun 5, 2025

Preview links (active after the build_preview check completes)

New or renamed files

Copy link
Contributor

@cswatt cswatt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

sorry for this annoying review!

I think my main concerns were:

  • Clarity on what the general topic of this page is vs. what the Preview feature is. Seems to me like this is about ticketing management for security, then narrows to this specific bidirectional syncing feature for Jira and Code Security, and the latter is what's in Preview.
  • "Bidirectional case management integration with Jira" is a very long string to parse as one entity. I noticed a comment in your ticket that says the feature name is "Case Management and Jira Bidirectional Syncing", so I've made a few suggestions to refer to the feature as "bidirectional syncing with Jira"
  • Setup steps have kind of an awkward format
  • other smaller edits/suggestions
  • Also note the preprod bits logo is visible in one of the screenshots!


### Bidirectional case management facets

There are several case management facets, including:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what entities are these facets attached to? the vulnerabilities, the case management projects, etc.?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

you mean their parent category? Triage.

michaelcretzman and others added 6 commits June 9, 2025 09:47
incorporating some peer review suggestions

Co-authored-by: cecilia saixue watt <cecilia.watt@datadoghq.com>
Co-authored-by: cecilia saixue watt <cecilia.watt@datadoghq.com>
@michaelcretzman michaelcretzman requested a review from cswatt June 9, 2025 20:33
@michaelcretzman michaelcretzman merged commit b037180 into master Jun 9, 2025
20 of 21 checks passed
@michaelcretzman michaelcretzman deleted the mcretzman/DOCS-10841-bidir-casemgmt-jira-codesec branch June 9, 2025 20:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Architecture Everything related to the Doc backend editorial review Waiting on a more in-depth review Images Images are added/removed with this PR okr11
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants