From 2d4b89940d5f170259c524c8e1cb1e70320ab2e5 Mon Sep 17 00:00:00 2001
From: Amanda Rueda <2890431-amandarueda@users.noreply.gitlab.com>
Date: Tue, 1 Oct 2024 17:30:30 +0000
Subject: [PATCH] Apply 1 suggestion(s) to 1 file(s)

Co-authored-by: Phillip Wells <pwells@gitlab.com>
---
 doc/user/group/epics/index.md | 37 +++++++++++++++++++++++++----------
 1 file changed, 27 insertions(+), 10 deletions(-)

diff --git a/doc/user/group/epics/index.md b/doc/user/group/epics/index.md
index 7b13fe25c6833..c6e4b77bbd5c3 100644
--- a/doc/user/group/epics/index.md
+++ b/doc/user/group/epics/index.md
@@ -47,21 +47,38 @@ goals in the set time frames, driving successful project outcomes.
   <iframe src="https://www.youtube-nocookie.com/embed/c0EwYYUZppw" frameborder="0" allowfullscreen> </iframe>
 </figure>
 
-## Relationships between epics and issues
+## Relationships between epics and other items
 
-The possible relationships between epics and issues are:
+The possible relationships between epics and other items are:
 
 - An epic is the parent of one or more issues.
 - An epic is the parent of one or more [child epics](manage_epics.md#multi-level-child-epics). Ultimate only.
+- An epic is [linked](linked_epics.md) to one or more task, objective, or key result.
+  Your administrator must have [enabled the new look for epics](epic_work_items.md).
+
+Example set of relationships:
 
 ```mermaid
+
 %%{init: { "fontFamily": "GitLab Sans" }}%%
 graph TD
-accTitle: Epics and issues
-accDescr: How issues and child epics relate to parent epics
-    Parent_epic --> Issue1
-    Parent_epic --> Child_epic
-    Child_epic --> Issue2
+    accTitle: Epics and issues
+    accDescr: How issues and child epics relate to parent epics and lateral relationships to work items
+
+    %% Main structure %%
+    Parent_epic -->|contains| Issue1
+    Parent_epic -->|contains| Child_epic
+    Child_epic -->|contains| Issue2
+
+    %% Additional work items and lateral relationships %%
+    Issue1 -- contains --> Task1["Task"]
+    Issue2 -- "blocked by" --> Objective1["Objective"]
+    Task1 -- blocking --> KeyResult1["Key Result"]
+
+    %% Work items linked to epics and issues %%
+    Parent_epic -. related .- Objective1
+    Child_epic -. "blocked by" .- KeyResult1
+
 ```
 
 ### Child issues from different group hierarchies
@@ -81,8 +98,8 @@ DETAILS:
 **Offering:** GitLab.com, Self-managed, GitLab Dedicated
 
 If your epic contains one or more [child epics](manage_epics.md#multi-level-child-epics) that
-have a start or due date, a visual
-[roadmap](../roadmap/index.md) of the child epics is listed under the parent epic.
+have a start or due date, you can go to a [roadmap](../roadmap/index.md)
+of the child epics from the epic.
 
 ![Child epics roadmap](img/epic_view_roadmap_v12_9.png)
 
@@ -102,7 +119,7 @@ A roadmap filtered for the parent epic opens.
 - [Turn on notifications](../../profile/notifications.md) for about epic events.
 - [Add an emoji reaction](../../emoji_reactions.md) to an epic or its comments.
 - Collaborate on an epic by posting comments in a [thread](../../discussions/index.md).
-- Use [health status](../../project/issues/managing_issues.md#health-status) to track your progress.
+- Use [health status](manage_epics.md#health-status) to track your progress.
 
 <!-- ## Troubleshooting
 
-- 
GitLab