fix links

Author: paulOsinski

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/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](/issue_tracking/jira/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/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](/issue_tracking/jira/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/jira_guide#enable-engagement-epic-mapping-for-products)**.
+For more information on this setting, see **[Enable Engagement Epic Mapping](/issue_tracking/jira/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/jira_guide#engagement-level-jira-settings)**.
+These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/issue_tracking/jira/jira_guide#engagement-level-jira-settings)**.

docs/content/asset_modelling/engagements_tests/PRO__engagements.md

@@ -129,7 +129,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/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](/issue_tracking/jira/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 
 
@@ -167,13 +167,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/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](/issue_tracking/jira/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/jira_guide#enable-engagement-epic-mapping-for-products)**.
+For more information on this setting, see **[Enable Engagement Epic Mapping](/issue_tracking/jira/jira_guide#enable-engagement-epic-mapping-for-products)**.
 
 ### Engagement-Level Jira Settings
 
@@ -185,4 +185,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/jira_guide#engagement-level-jira-settings)**.
+These settings are accessible from the **Edit Engagement** page. For more details, see **[Engagement-Level Jira Settings](/issue_tracking/jira/jira_guide#engagement-level-jira-settings)**.