Skip to content

docs(pro): mark the third wave of Pro feature flags as generally available - #16416

Open
devGregA wants to merge 1 commit into
DefectDojo:devfrom
devGregA:docs/third-wave-flags-ga
Open

devGregA wants to merge 1 commit into
DefectDojo:devfrom
devGregA:docs/third-wave-flags-ga

Conversation

@devGregA

@devGregA devGregA commented Oct 19, 2026 •

Copy link
Copy Markdown
Contributor

Summary

Five DefectDojo Pro features become generally available in the next release: on for every Pro instance, Cloud and On-Premise, and no longer listed on Settings > Feature Flags. This PR updates the docs so no page still tells an administrator to turn them on there.

  • Triage Engine (listed as Rules Engine 2.0 (Graph Editor))
  • Messaging Connectors
  • Customizable Dashboards (listed as Dashboards 2.0)
  • Customizable Page Layouts
  • AI Threat Modeling (still requires the Sensei license)

What changed

  • Feature Flags page: the five join the "always on" list and their rows leave the feature reference. MCP: Dashboards 2.0 now only needs the MCP server, since Customizable Dashboards no longer has a flag of its own.
  • Feature pages: the beta, off-by-default and "turn it on from Feature Flags" wording and the enabling steps are removed from the Triage Engine (about, conversion guide, webhook receivers), Messaging Connectors, Customizable Dashboards (plus its API and LLM guides), Command Center, Dashboard introduction, Report Builder (plus API), MCP server, Page Layouts, Sidebar, Menu Badges, Threat Modeling and PAIN ratings setup pages, plus the Pro and Open-Source UI comparison page and the Sidebar's list of flag-gated entries (both refreshed on dev in docs(about): refresh the edition comparison, Pro UI, sidebar and FAQ pages #16412). The "Enabling ..." sections become "Where to find ...".
  • Classic tile dashboard: the Customizable Dashboards and Sidebar pages now say the Dashboards entry replaces the classic tile dashboard.
  • Translations: the de, es, fr, it, ja, pt-br and zh-hans copies are updated in step wherever they carry the same text.

Unchanged: the original Rules Engine, Compliance and the framework packs, and the MCP toolset flags, which remain opt-in.

Testing

Docs only. Every English page was checked against the new behavior, and every locale was searched for leftover enable or beta wording about these five features. Links touched in this PR point to pages and anchors that exist on dev.

🤖 Generated with Claude Code

@github-actions

Copy link
Copy Markdown
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

…lable

Triage Engine (Rules Engine 2.0), Messaging Connectors, Customizable
Dashboards (Dashboards 2.0), Customizable Page Layouts and AI Threat
Modeling are now always on in DefectDojo Pro and no longer listed on
Settings > Feature Flags.

- Feature Flags page: add the five to the "always on" list and drop
  their rows from the feature reference; MCP: Dashboards 2.0 now only
  requires the MCP server.
- Remove the beta / off-by-default / turn-it-on-from-Feature-Flags
  wording and enabling steps from the Triage Engine, Messaging
  Connectors, Customizable Dashboards (+ API and LLM guides), Command
  Center, Report Builder, MCP server, Page Layouts, Sidebar, Menu Badges,
  Threat Modeling and PAIN ratings setup pages.
- Mirror the changes in the de, es, fr, it, ja, pt-br and zh-hans
  copies where they carry the same text.

AI Threat Modeling still requires the Sensei licence. The original
Rules Engine, Compliance and the framework packs are unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Conflicts have been resolved. A maintainer will review the pull request shortly.

@github-actions

Copy link
Copy Markdown
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant