point internal links directly at new /connections/ paths

paulOsinski · paulOsinski · commit 893b2c8540f9 · 2026-07-16T14:44:12.000-04:00
diff --git a/docs/content/asset_modelling/engagements_tests/OS__engagements.md b/docs/content/asset_modelling/engagements_tests/OS__engagements.md
@@ -120,7 +120,7 @@ Once closed, the Engagement’s status will be changed to “Completed.” Never
 
 Closing an Engagement does not change the status of the Findings within any of the Engagement’s Tests. Findings remain open, mitigated, or risk accepted according to their own lifecycle, and remain accessible for viewing and reporting.
 
-If the Engagement is linked to a Jira Epic (see **[Jira Integration: Enable Engagement Epic Mapping](/issue_tracking/jira/os__jira_guide/#enable-engagement-epic-mapping-for-products)**), closing the Engagement will trigger an asynchronous task that closes the associated Jira Epic in your connected Jira Space.
+If the Engagement is linked to a Jira Epic (see **[Jira Integration: Enable Engagement Epic Mapping](/connections/os_jira/os__jira_guide/#enable-engagement-epic-mapping-for-products)**), closing the Engagement will trigger an asynchronous task that closes the associated Jira Epic in your connected Jira Space.
 
 ### Reopen Engagements 
 
@@ -160,13 +160,13 @@ For auditing purposes, it is recommended to close any completed Engagements, rat
 
 ## Jira Integration
 
-Engagements can be linked to a connected Jira Space, allowing Findings within the Engagement to be pushed to Jira as Issues. For a complete guide to setting up Jira, see **[Connecting DefectDojo to Jira](/issue_tracking/jira/os__jira_guide/)**.
+Engagements can be linked to a connected Jira Space, allowing Findings within the Engagement to be pushed to Jira as Issues. For a complete guide to setting up Jira, see **[Connecting DefectDojo to Jira](/connections/os_jira/os__jira_guide/)**.
 
 ### Engagement Epic Mapping
 
 When **Enable Engagement Epic Mapping** is checked in a Product's Jira settings, Engagements will be pushed to Jira as Epics. Findings within the Engagement are pushed as child Issues underneath the Epic, mirroring DefectDojo's Engagement → Findings hierarchy in Jira's Epic → Issue structure.
 
-For more information on this setting, see **[Enable Engagement Epic Mapping](/issue_tracking/jira/os__jira_guide/#enable-engagement-epic-mapping-for-products)**.
+For more information on this setting, see **[Enable Engagement Epic Mapping](/connections/os_jira/os__jira_guide/#enable-engagement-epic-mapping-for-products)**.
 
 ### Engagement-Level Jira Settings
 
@@ -178,4 +178,4 @@ By default, Engagements inherit their Jira settings from their parent Product. H
 - **Jira Labels** — tag Issues with Engagement-specific labels
 - **Default Assignee** — assign Issues to a different team member
 
-These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/issue_tracking/jira/os__jira_guide/#engagement-level-jira-settings)**.
+These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/connections/os_jira/os__jira_guide/#engagement-level-jira-settings)**.
diff --git a/docs/content/asset_modelling/engagements_tests/PRO__assets.md b/docs/content/asset_modelling/engagements_tests/PRO__assets.md
@@ -145,7 +145,7 @@ In DefectDojo Pro, Connectors are mapped to different Assets in DefectDojo Pro,
 
 Once a Connector has been attached to an Asset, it will import scan results and create or update Engagements, Tests, and Findings within that Asset.
 
-For more information about Connectors, click [here](/import_data/pro/connectors/about_connectors/#main-content). 
+For more information about Connectors, click [here](/connections/upstream/about/#main-content). 
 
 ### CI/CD Pipelines 
 
@@ -168,7 +168,7 @@ This means that the same vulnerability may receive a different Priority or Risk
 
 ### Jira / Integrators Relationships
 
-Assets can be mapped directly to [Jira](/issue_tracking/jira/pro__jira_guide/#main-content) or [Integrators](/issue_tracking/pro_integration/integrations_toolreference/#main-content) instances (e.g. GitHub, GitLab, ServiceNow, etc.), which push the Asset’s Findings outward into external ticketing/work-management systems.
+Assets can be mapped directly to [Jira](/connections/downstream/pro__jira_guide/#main-content) or [Integrators](/connections/downstream/downstream_toolreference/#main-content) instances (e.g. GitHub, GitLab, ServiceNow, etc.), which push the Asset’s Findings outward into external ticketing/work-management systems.
 
 Because Findings inherit risk, priority, and ownership from their parent Asset, the Asset effectively determines the remediation context that flows into Jira tickets and Integrator workflows.
 
diff --git a/docs/content/asset_modelling/engagements_tests/PRO__engagements.md b/docs/content/asset_modelling/engagements_tests/PRO__engagements.md
@@ -133,7 +133,7 @@ Engagements are closed by selecting **Close Engagement** within the Engagement
 
 Closing an Engagement does not change the status of the Findings within any of the Engagement’s Tests. Findings remain open, mitigated, or risk accepted according to their own lifecycle, and remain accessible for viewing and reporting.
 
-If the Engagement is linked to a Jira Epic (see **[Jira Integration: Enable Engagement Epic Mapping](/issue_tracking/jira/pro__jira_guide/#enable-engagement-epic-mapping)**), closing the Engagement will trigger an asynchronous task that closes the associated Jira Epic in your connected Jira Space.
+If the Engagement is linked to a Jira Epic (see **[Jira Integration: Enable Engagement Epic Mapping](/connections/downstream/pro__jira_guide/#enable-engagement-epic-mapping)**), closing the Engagement will trigger an asynchronous task that closes the associated Jira Epic in your connected Jira Space.
 
 ### Reopen Engagements 
 
@@ -171,13 +171,13 @@ For auditing purposes, it is recommended to close any completed Engagements, rat
 
 ## Jira Integration
 
-Engagements can be linked to a connected Jira Space, allowing Findings within the Engagement to be pushed to Jira as Issues. For a complete guide to setting up Jira, see **[Connecting DefectDojo to Jira](/issue_tracking/jira/pro__jira_guide/)**.
+Engagements can be linked to a connected Jira Space, allowing Findings within the Engagement to be pushed to Jira as Issues. For a complete guide to setting up Jira, see **[Connecting DefectDojo to Jira](/connections/downstream/pro__jira_guide/)**.
 
 ### Engagement Epic Mapping
 
 When **Enable Engagement Epic Mapping** is checked in a Product’s Jira settings, Engagements will be pushed to Jira as Epics. Findings within the Engagement are pushed as child Issues underneath the Epic, mirroring DefectDojo’s Engagement → Findings hierarchy in Jira’s Epic → Issue structure.
 
-For more information on this setting, see **[Enable Engagement Epic Mapping](/issue_tracking/jira/pro__jira_guide/#enable-engagement-epic-mapping)**.
+For more information on this setting, see **[Enable Engagement Epic Mapping](/connections/downstream/pro__jira_guide/#enable-engagement-epic-mapping)**.
 
 ### Engagement-Level Jira Settings
 
@@ -189,4 +189,4 @@ By default, Engagements inherit their Jira settings from their parent Asset (Pro
 - **Jira Labels** — tag Issues with Engagement-specific labels
 - **Default Assignee** — assign Issues to a different team member
 
-These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/issue_tracking/jira/pro__jira_guide/#engagement-level-jira-settings)**.
+These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/connections/downstream/pro__jira_guide/#engagement-level-jira-settings)**.
diff --git a/docs/content/asset_modelling/engagements_tests/PRO__tests.md b/docs/content/asset_modelling/engagements_tests/PRO__tests.md
@@ -43,7 +43,7 @@ DefectDojo parses the provided data, creates a new Test (or imports into an exis
 
 #### Connectors 
 
-[**Connectors**](/import_data/pro/connectors/about_connectors) can be used to automatically ingest and organize vulnerability data from external tools via API calls. Once configured, a Connector fetches scan results, parses the data, and creates new Tests or updates existing Tests depending on its configuration. Findings are then attached to the corresponding Test.
+[**Connectors**](/connections/upstream/about_connectors) can be used to automatically ingest and organize vulnerability data from external tools via API calls. Once configured, a Connector fetches scan results, parses the data, and creates new Tests or updates existing Tests depending on its configuration. Findings are then attached to the corresponding Test.
 
 #### Test Creation Mechanism Comparison 
 
diff --git a/docs/content/get_started/about/OS__new_user_checklist.md b/docs/content/get_started/about/OS__new_user_checklist.md
@@ -23,6 +23,6 @@ This is the essence of DefectDojo - import security data, organize it, and prese
 All of these features can be automated, and because DefectDojo can handle over 200 tools (at time of writing) you should be all set to create a functional security inventory of your entire organizational output.
 
 ### Open-Source Features
-- Does your organization use Jira? Learn how to use our [Jira integration](/issue_tracking/jira/os__jira_guide/) to create Jira tickets from the data you ingest.
+- Does your organization use Jira? Learn how to use our [Jira integration](/connections/os_jira/os__jira_guide/) to create Jira tickets from the data you ingest.
 - Are you expecting to share DefectDojo with many users in your organization? Check out our guides to [user management](/admin/user_management/about_perms_and_roles/) and set up role-based access control (RBAC).
 - Ready to dive into automation? Learn how to use the [DefectDojo API](/import_data/import_scan_files/api_pipeline_modelling/) to automatically import new data, and build a robust CI/CD pipeline.
diff --git a/docs/content/get_started/about/PRO__new_user_checklist.md b/docs/content/get_started/about/PRO__new_user_checklist.md
@@ -25,4 +25,4 @@ All of these features can be automated, and because DefectDojo can handle over 2
 ### Pro Features
 - If your organization uses Jira, ServiceNow, AzureDevops, GitHub or GitLab for issue tracking, check out our [documentation](/issue_tracking/intro/intro/) on those integrations.
 - Customize your [main Dashboard](/metrics_reports/dashboards/introduction_dashboard/) with filtered tiles to view your environment at a glance.
-- Learn how to rapidly import data and mirror your team's existing security environment with [Connectors](/import_data/pro/connectors/about_connectors/).
+- Learn how to rapidly import data and mirror your team's existing security environment with [Connectors](/connections/upstream/about/).
diff --git a/docs/content/get_started/about/about_defectdojo.md b/docs/content/get_started/about/about_defectdojo.md
@@ -81,7 +81,7 @@ If you run into trouble with an Open-Source install, we highly recommend asking
 
 DefectDojo Inc. hosts a Pro edition of this software for commercial purposes.  Along with a sleek, modern UI, DefectDojo Pro includes:
 
-* [Connectors](/import_data/pro/connectors/about_connectors/): out-of-the-box API integrations with enterprise-level scanners (such as Checkmarx One, BurpSuite, Semgrep and more)
+* [Connectors](/connections/upstream/about/): out-of-the-box API integrations with enterprise-level scanners (such as Checkmarx One, BurpSuite, Semgrep and more)
 * **Configurable Import Methods**: [Universal Parser](/supported_tools/parsers/universal_parser/), [Smart Upload](/import_data/pro/specialized_import/smart_upload/)
 * **[CLI Tools](/import_data/pro/specialized_import/external_tools/)** for rapid integration with your systems
 * **[Additional Project Tracking Integrations](/issue_tracking/intro/intro/)**: ServiceNow, Azure DevOps, GitHub and GitLab
diff --git a/docs/content/get_started/about/faq.md b/docs/content/get_started/about/faq.md
@@ -42,7 +42,7 @@ DefectDojo Pro expands on the above workflows further, adding:
   - An optimized upload method which processes Findings in the background.
   - The ability to quickly build a [command-line pipeline](/import_data/pro/specialized_import/external_tools/) using our Universal Importer and DefectDojo CLI apps, allowing you to easily import, reimport, and export data to your DefectDojo Pro instance.
   - A [Universal Parser](/import_data/pro/specialized_import/universal_parser/) to turn any .json or .csv report into an actional set of Findings and have DefectDojo Pro will parse the data however you like.
-  - [Connectors](/import_data/pro/connectors/about_connectors/), which provide an instant connection to supported tools to import new Finding data so you can get an automated Import pipeline established without the need to set up any API calls or cron jobs.
+  - [Connectors](/connections/upstream/about/), which provide an instant connection to supported tools to import new Finding data so you can get an automated Import pipeline established without the need to set up any API calls or cron jobs.
 
 ### How does DefectDojo handle access control?
 
diff --git a/docs/content/get_started/about/ui_pro_vs_os.md b/docs/content/get_started/about/ui_pro_vs_os.md
@@ -13,7 +13,7 @@ The Pro UI brings the following enhancements to DefectDojo:
 
 - Modern and sleek design using Vue.js.
 - Optimized data delivery and load times, especially for large datasets.
-- Access to new Pro features, including [API Connectors](/import_data/pro/connectors/about_connectors/), [Universal Importer](/import_data/pro/specialized_import/external_tools/), and [Pro Metrics](https://docs.defectdojo.com/metrics_reports/pro_metrics/pro__overview/) views.
+- Access to new Pro features, including [API Connectors](/connections/upstream/about/), [Universal Importer](/import_data/pro/specialized_import/external_tools/), and [Pro Metrics](https://docs.defectdojo.com/metrics_reports/pro_metrics/pro__overview/) views.
 - Improved UI workflows: better filtering, dashboards, and navigation.
 
 ## Switching To The Pro UI
@@ -30,7 +30,7 @@ To access the Pro UI, open your User Options menu from the top-right hand corner
 
 2. The Homepage, [AI-powered native API connection capabilities](/metrics_reports/ai/mcp_server_pro/), Pro Metrics, and the Calendar view are all accessible under Dashboards.
 
-4. Import methods can be found in the Import section: set up [API Connectors](/import_data/pro/connectors/about_connectors/), use the [Add Findings](/import_data/import_scan_files/pro__import_scan_ui/) form to Add Findings, use [Smart Upload](/import_data/pro/specialized_import/smart_upload/) to handle infrastructure scanning tools, or use our external tools—[Universal Importer and DefectDojo CLI](/import_data/pro/specialized_import/external_tools/)—to streamline both the import and reimport processes of Findings and associated objects.
+4. Import methods can be found in the Import section: set up [API Connectors](/connections/upstream/about/), use the [Add Findings](/import_data/import_scan_files/pro__import_scan_ui/) form to Add Findings, use [Smart Upload](/import_data/pro/specialized_import/smart_upload/) to handle infrastructure scanning tools, or use our external tools—[Universal Importer and DefectDojo CLI](/import_data/pro/specialized_import/external_tools/)—to streamline both the import and reimport processes of Findings and associated objects.
 
 5. The **Manage** section allows you to view different objects in the [Product Hierarchy](/asset_modelling/os_hierarchy/product_hierarchy/), with views for Product Types, Products, Engagements, Tests, Findings, Risk Acceptances, Endpoints, and Components.  There are additional sections for generating reports (Report Builder), using surveys (Surveys), as well as a [Rules Engine](/automation/rules_engine/about/). 
 
diff --git a/docs/content/get_started/pro/pro_features.md b/docs/content/get_started/pro/pro_features.md
@@ -59,7 +59,7 @@ See our [Deduplication Tuning Guide](/triage_findings/finding_deduplication/pro_
 
 ### More Import Options
 
-DefectDojo Pro includes four additional import methods: [Universal Importer](/import_data/pro/specialized_import/external_tools/), [API Connectors](/import_data/pro/connectors/about_connectors/), [Universal Parser](/supported_tools/parsers/universal_parser/), and [Smart Upload](/import_data/pro/specialized_import/smart_upload/).
+DefectDojo Pro includes four additional import methods: [Universal Importer](/import_data/pro/specialized_import/external_tools/), [API Connectors](/connections/upstream/about/), [Universal Parser](/supported_tools/parsers/universal_parser/), and [Smart Upload](/import_data/pro/specialized_import/smart_upload/).
 
 ![image](images/pro_import_methods.png)
 
@@ -78,7 +78,7 @@ See our [External Tools Guide](/import_data/pro/specialized_import/external_tool
 
 DefectDojo can instantly connect to enterprise-level scanning tools to import new Finding data, creating an automated Import pipeline that works out-of-the-box without the need to set up any API calls or cron jobs. 
 
-See our [Connectors Guide](/import_data/pro/connectors/about_connectors/) for more information.
+See our [Connectors Guide](/connections/upstream/about/) for more information.
 
 ![image](images/add_edit_connectors_2.png)
 
diff --git a/docs/content/import_data/import_intro/comparison.md b/docs/content/import_data/import_intro/comparison.md
@@ -21,7 +21,7 @@ There are two main ways that DefectDojo can upload Finding reports.
 <span style="background-color:rgba(242, 86, 29, 0.3)">DefectDojo Pro</span> users have an additional three methods to handle reports and data:
 
 * Via **Universal Importer** or **DefectDojo CLI**, command line tools which leverage the DefectDojo API: See [Universal Importer & DefectDojo-CLI guides](/import_data/pro/specialized_import/external_tools/)
-* Via **Connectors** for certain tools, an ‘out of the box’ data integration: See [Connectors Guide](/import_data/pro/connectors/about_connectors/)
+* Via **Connectors** for certain tools, an ‘out of the box’ data integration: See [Connectors Guide](/connections/upstream/about/)
 * Via **Smart Upload** for certain tools, an importer designed to handle infrastructure scans: See [Smart Upload Guide](/import_data/pro/specialized_import/smart_upload/)
 
 ### Comparing Upload Methods
diff --git a/docs/content/issue_tracking/intro/intro.md b/docs/content/issue_tracking/intro/intro.md
@@ -10,8 +10,8 @@ The DefectDojo issue tracking integrations connect your vulnerability management
 
 | Edition      | Supported Issue Tracking Integrations |
 |--------------|---------------------------------------|
-| Community Edition  | * [Jira](/issue_tracking/jira/os__jira_guide/)                          |
-| Pro          | * [Jira](/issue_tracking/jira/pro__jira_guide/)<br>* [Azure DevOps](/issue_tracking/pro_integration/integrations_toolreference/#azure-devops-boards)<br>* [GitHub](/issue_tracking/pro_integration/integrations_toolreference/#github)<br>* [GitLab Boards](/issue_tracking/pro_integration/integrations_toolreference/#gitlab)<br>* [ServiceNow](/issue_tracking/pro_integration/integrations_toolreference/#servicenow) |
+| Community Edition  | * [Jira](/connections/os_jira/os__jira_guide/)                          |
+| Pro          | * [Jira](/connections/downstream/pro__jira_guide/)<br>* [Azure DevOps](/connections/downstream/downstream_toolreference/#azure-devops-boards)<br>* [GitHub](/connections/downstream/downstream_toolreference/#github)<br>* [GitLab Boards](/connections/downstream/downstream_toolreference/#gitlab)<br>* [ServiceNow](/connections/downstream/downstream_toolreference/#servicenow) |
 
 
 When enabled, DefectDojo can create issues automatically, or selectively from Products or Engagement. As Findings are updated in DefectDojo—resolved, mitigated, or reactivated—the corresponding issues can be kept in sync, ensuring both systems reflect the current state of risk.
diff --git a/docs/content/onprem_deployment/forward_proxy.md b/docs/content/onprem_deployment/forward_proxy.md
@@ -50,4 +50,4 @@ The proxy configuration documented here applies to **outbound** calls *from* Def
 
 The most common case where this matters is Jira's bidirectional sync, which relies on Jira posting webhooks to DefectDojo's `/jira/webhook/<secret>` endpoint when issues change.  If DefectDojo is behind a firewall that prevents Jira from reaching it directly, setting `HTTPS_PROXY` will not solve that — you will need to address the inbound networking separately (a reverse proxy / load balancer with the appropriate firewall rules, an inbound NAT rule, or similar).
 
-For Jira-specific troubleshooting, see [Troubleshooting Jira errors](/issue_tracking/jira/troubleshooting_jira/).
+For Jira-specific troubleshooting, see [Troubleshooting Jira errors](/connections/downstream/troubleshooting_jira/).
diff --git a/docs/content/supported_tools/_index.md b/docs/content/supported_tools/_index.md
@@ -24,7 +24,7 @@ DefectDojo can parse data from 200+ security reports and counting.
 
 **Smart Upload** allows you to split infrastructure-wide scan files up by component or endpoint, and easily combine those results with other Findings from the same location.
 
-| [Connectors](/import_data/pro/connectors/about_connectors/): supported tools | [Smart Upload](/import_data/pro/specialized_import/smart_upload/): supported tools |
+| [Connectors](/connections/upstream/about/): supported tools | [Smart Upload](/import_data/pro/specialized_import/smart_upload/): supported tools |
 | --- | --- |
 | Anchore, AWS Security Hub, BurpSuite, Checkmarx ONE, Dependency-Track, Probely, Semgrep, SonarQube, Snyk, Tenable | Nexpose, NMap, OpenVas, Qualys, Tenable, Wiz | 
 
diff --git a/docs/content/supported_tools/parsers/_index.md b/docs/content/supported_tools/parsers/_index.md
diff --git a/docs/content/supported_tools/parsers/file/wiz.md b/docs/content/supported_tools/parsers/file/wiz.md
