issue ownership set up + ome menu rearranging

config/_default/menus/main.en.yaml

@@ -2096,41 +2096,46 @@ menu:
       parent: error_tracking
       identifier: error_tracking_states
       weight: 2
-    - name: Suspected Causes
-      url: error_tracking/suspected_causes
-      parent: error_tracking
-      identifier: error_tracking_suspected_causes
-      weight: 3
     - name: Regression Detection
       url: error_tracking/regression_detection
       parent: error_tracking
       identifier: error_tracking_regression_detection
-      weight: 4
-    - name: Default Grouping
-      url: error_tracking/default_grouping
-      parent: error_tracking
-      identifier: error_tracking_default_grouping
-      weight: 5
+      weight: 3
     - name: Monitors
       url: error_tracking/monitors
       parent: error_tracking
       identifier: error_tracking_monitors
-      weight: 6
-    - name: Custom Grouping
-      url: error_tracking/custom_grouping
+      weight: 4
+    - name: Suspected Causes
+      url: error_tracking/suspected_causes
       parent: error_tracking
-      identifier: error_tracking_custom_grouping
-      weight: 7
+      identifier: error_tracking_suspected_causes
+      weight: 5
+    - name: Issue Ownership
+      url: error_tracking/issue_ownership
+      parent: error_tracking
+      identifier: error_tracking_issue_ownership
+      weight: 6
     - name: Identify Suspect Commits
       url: error_tracking/suspect_commits
       parent: error_tracking
       identifier: error_tracking_suspect_commits
+      weight: 7
+    - name: Default Grouping
+      url: error_tracking/default_grouping
+      parent: error_tracking
+      identifier: error_tracking_default_grouping
       weight: 8
+    - name: Custom Grouping
+      url: error_tracking/custom_grouping
+      parent: error_tracking
+      identifier: error_tracking_custom_grouping
+      weight: 9
     - name: Track Browser and Mobile Errors
       url: error_tracking/frontend
       parent: error_tracking
       identifier: error_tracking_frontend
-      weight: 9
+      weight: 10
     - name: Browser Error Tracking
       url: error_tracking/frontend/browser
       parent: error_tracking_frontend
@@ -2160,7 +2165,7 @@ menu:
       url: error_tracking/backend
       parent: error_tracking
       identifier: error_tracking_backend
-      weight: 10
+      weight: 11
     - name: Exception Replay
       url: error_tracking/backend/exception_replay
       parent: error_tracking_backend
@@ -2180,12 +2185,17 @@ menu:
       url: error_tracking/manage_data_collection
       parent: error_tracking
       identifier: error_tracking_manage_data
-      weight: 11
+      weight: 12
+    - name: Dynamic Sampling
+      url: error_tracking/dynamic_sampling
+      parent: error_tracking
+      identifier: error_tracking_dynamic_sampling
+      weight: 13
     - name: Troubleshooting
       url: error_tracking/troubleshooting
       parent: error_tracking
       identifier: error_tracking_troubleshooting
-      weight: 12
+      weight: 14
     - name: Change Tracking
       url: change_tracking/
       pre: graph-3

content/en/error_tracking/issue_ownership.md

@@ -0,0 +1,48 @@
+---
+title: Error Tracking Issue Ownership
+is_beta: true
+private: false
+description: Learn about how to set issue owners to ensure that you are seeing the issues that matter to you.
+further_reading:
+- link: '/error_tracking/suspect_commits'
+  tag: 'Documentation'
+  text: 'Learn about how Error Tracking can identify suspect commits'
+- link: '/error_tracking'
+  tag: 'Documentation'
+  text: 'Learn about Error Tracking'
+---
+
+{{< beta-callout url="https://www.datadoghq.com/product-preview/auto-filter-assign-error-tracking-issues/" btn_hidden="false"  >}}
+Issue Ownership for Error Tracking is currently in Preview.
+{{< /beta-callout >}}
+
+## Overview
+
+Defining issue ownership allows you to discard irrelevant information to help  prioritize and focus on what matters. Error Tracking leverages the GitHub CODEOWNERS file to link issues to the relevant person or team for focused investigations.
+
+We can automatically filter the list of issues, alert the owning teams, and assign issues automatically to the suspect commit author. Datadog defines ownership based on Datadog teams with code owners, service owners, and view owners. Assignees are assigned based on the suspect commit or through manual assigns. 
+
+
+## Setup
+
+1. Ensure that you have [Source Code Integration][1] set up for your [backend services][2] and [frontend applications][3]. 
+2. [Configure your GitHub repository][4] with the `Members Read` permission. If you already have a GitHub app created, you can see if you have the proper permissions listed under **Link GitHub teams with Datadog teams** feature. 
+
+{{< img src="error_tracking/issue-owner-github-setup.png" alt="Error Tracking Issue Ownership GitHub Setup" style="width:90%" >}}
+
+3. Link your Datadog Team to your Datadog Team
+Navigate to **Organization Settings** > **Teams** > Select your team > **Settings** > **GitHub Connection** and search for the GitHub team(s) you'd like to connect with your Datadog Team. 
+
+{{< img src="/error_tracking/github_connection_setup.mp4" alt="Link your GitHub team to Datadog team" video=true >}}
+
+
+
+
+## Further Reading
+
+{{< partial name="whats-next/whats-next.html" >}}
+
+[1]: /integrations/guide/source-code-integration/
+[2]: https://app.datadoghq.com/source-code/setup/apm
+[3]: https://app.datadoghq.com/source-code/setup/rum
+[4]: https://app.datadoghq.com/integrations/github/configuration?