Skip to content

[SEC-27541] Restrict CSM Jira issues page to GovCloud only#34973

Merged
FredMoster merged 1 commit intomasterfrom
frederic.moster/hide_legacy_jira_feature
Mar 6, 2026
Merged

[SEC-27541] Restrict CSM Jira issues page to GovCloud only#34973
FredMoster merged 1 commit intomasterfrom
frederic.moster/hide_legacy_jira_feature

Conversation

@FredMoster
Copy link
Contributor

@FredMoster FredMoster commented Mar 3, 2026

What does this PR do? What is the motivation?

SEC-27541

The "Create Jira Issues for Cloud Security Issues" feature is deprecated on all Datadog sites except GovCloud (US1-FED / ddog-gov.com). This PR restricts the page accordingly:

  • Adds csm_jira: [us,us3,us5,eu,ap1,ap2] to the unsupported_sites map in params.yaml, so the site-support banner system recognizes the feature as unsupported on non-GovCloud sites.
  • Adds site_support_id: csm_jira to the page front matter, causing a red alert banner to render for non-GovCloud users who visit the URL directly.
  • Removes the "Create Jira Issues" entry from the sidebar navigation.
  • Removes the nextlink to the Jira page from the review_remediate/_index.md parent page.

GovCloud users are unaffected: the page renders normally with no banner, as gov is not in the unsupported list.

Merge instructions

Merge readiness:

  • Ready for merge

Additional notes

Verification:

  1. Navigate to /security/cloud_security_management/review_remediate/ — "Create Jira Issues" should not appear in the sidebar nav or the whatsnext links.
  2. Visit /security/cloud_security_management/review_remediate/jira directly:
    • With site selector set to a non-gov site (e.g. US1) → red alert banner appears.
    • With site selector set to US1-FED → no banner, page content displays normally.

@github-actions github-actions bot added the Architecture Everything related to the Doc backend label Mar 3, 2026
@FredMoster FredMoster force-pushed the frederic.moster/hide_legacy_jira_feature branch 3 times, most recently from 2ce999c to 54cceb3 Compare March 4, 2026 09:07
@FredMoster FredMoster marked this pull request as ready for review March 4, 2026 09:09
@FredMoster FredMoster requested review from a team as code owners March 4, 2026 09:09
getting_started_feature_flags: [gov]
gcp-private-service-connect: [us,us3,gov,ap1,ap2]
google-hangouts-chat: [gov]
csm_jira: [us,us3,us5,eu,ap1,ap2]
Copy link

Choose a reason for hiding this comment

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

I’m curious how this is going to be reflected in the doc since docs.datadoghq.com isn’t per DC

Copy link
Contributor Author

Choose a reason for hiding this comment

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

the page is still available but it shows this warning when a non-gov DC is selected
image

@buraizu buraizu self-assigned this Mar 4, 2026
@buraizu buraizu added the under_review Sent to someone outside of the docs team for review. label Mar 5, 2026
@FredMoster FredMoster force-pushed the frederic.moster/hide_legacy_jira_feature branch from 54cceb3 to 1b6bc39 Compare March 5, 2026 08:25
- Add csm_jira to unsupported_sites in params.yaml marking all non-gov sites as unsupported
- Add site_support_id: csm_jira to jira.md front matter to trigger the unsupported banner
- Remove Create Jira Issues entry from sidebar nav
- Remove nextlink to Jira page from review_remediate/_index.md

Rationale: The feature is being deprecated on all Datadog sites except GovCloud (us1.fed); non-GovCloud users visiting the URL directly will see an alert banner, while GovCloud users see the page normally.

This commit made by [/dd:git:commit:quick](https://github.com/DataDog/claude-marketplace/tree/main/dd/commands/git/commit/quick.md)
@FredMoster FredMoster force-pushed the frederic.moster/hide_legacy_jira_feature branch from 1b6bc39 to f256d89 Compare March 5, 2026 08:28
@FredMoster FredMoster merged commit 5ca760a into master Mar 6, 2026
23 of 24 checks passed
@FredMoster FredMoster deleted the frederic.moster/hide_legacy_jira_feature branch March 6, 2026 08:17
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 under_review Sent to someone outside of the docs team for review.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants