Add latest changes from gitlab-org/gitlab@master

3 files changed, 150 insertions, 48 deletions

diff --git a/.gitlab/CODEOWNERS b/.gitlab/CODEOWNERS
index 9d288cb3b34..2dfd9aa71ed 100644
--- a/.gitlab/CODEOWNERS
+++ b/.gitlab/CODEOWNERS
@@ -115,12 +115,6 @@ Dangerfile @gl-quality/eng-prod
 /ee/spec/frontend/license_compliance/components/detected_licenses_table_spec.js @gitlab-org/govern/threat-insights-frontend-team
 
 ^[Secure]
-/ee/lib/gitlab/ci/parsers/license_compliance/ @gitlab-org/secure/composition-analysis-be
-/ee/lib/gitlab/ci/parsers/security/ @gitlab-org/secure/composition-analysis-be @gitlab-org/secure/dynamic-analysis-be @gitlab-org/secure/static-analysis-be @gitlab-org/secure/fuzzing-be
-/ee/lib/gitlab/ci/reports/coverage_fuzzing/ @gitlab-org/secure/fuzzing-be
-/ee/lib/gitlab/ci/reports/dependency_list/ @gitlab-org/secure/composition-analysis-be
-/ee/lib/gitlab/ci/reports/license_scanning/ @gitlab-org/secure/composition-analysis-be
-/ee/lib/gitlab/ci/reports/security/ @gitlab-org/secure/composition-analysis-be @gitlab-org/secure/dynamic-analysis-be @gitlab-org/secure/static-analysis-be @gitlab-org/secure/fuzzing-be
 /ee/app/services/app_sec/dast/ @gitlab-org/secure/dynamic-analysis-be
 
 ^[Security Policies]
@@ -1372,6 +1366,16 @@ lib/gitlab/checks/** @proglottis @toon
 /lib/gitlab/ci/templates/Jobs/SAST.*.yml @gitlab-org/secure/static-analysis
 /lib/gitlab/ci/templates/Jobs/Secret-Detection.*.yml @gitlab-org/secure/static-analysis
 
+# Overrides for Verify. These files below require approval from teams outside Verify.
+/**/ci/reports/**/             @gitlab-org/maintainers/rails-backend
+/**/ci/parsers/**/             @gitlab-org/maintainers/rails-backend
+/ee/lib/gitlab/ci/parsers/license_compliance/ @gitlab-org/secure/composition-analysis-be
+/ee/lib/gitlab/ci/parsers/security/ @gitlab-org/govern/threat-insights-backend-team
+/ee/lib/gitlab/ci/reports/coverage_fuzzing/ @gitlab-org/secure/fuzzing-be
+/ee/lib/gitlab/ci/reports/dependency_list/ @gitlab-org/secure/composition-analysis-be
+/ee/lib/gitlab/ci/reports/license_scanning/ @gitlab-org/secure/composition-analysis-be
+/ee/lib/gitlab/ci/reports/security/ @gitlab-org/govern/threat-insights-backend-team
+
 [Manage::Workspace]
 lib/api/entities/basic_project_details.rb @gitlab-org/manage/manage-workspace/backend-approvers
 lib/api/entities/project_with_access.rb @gitlab-org/manage/manage-workspace/backend-approvers
diff --git a/.gitlab/ci/rules.gitlab-ci.yml b/.gitlab/ci/rules.gitlab-ci.yml
index d10803f025a..ddada0cf78f 100644
--- a/.gitlab/ci/rules.gitlab-ci.yml
+++ b/.gitlab/ci/rules.gitlab-ci.yml
@@ -619,6 +619,8 @@
 
 .rails:rules:ee-and-foss-default-rules:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
@@ -631,6 +633,8 @@
 
 .rails:rules:system-default-rules:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
@@ -645,6 +649,8 @@
 
 .rails:rules:previous-failed-tests-default-rules:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-security-merge-request
       when: never
     - <<: *if-merge-request-labels-run-all-rspec
@@ -811,6 +817,8 @@
   rules:
     - <<: *if-not-canonical-namespace
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-targeting-stable-branch
     - <<: *if-merge-request-labels-run-review-app
     - <<: *if-dot-com-gitlab-org-and-security-merge-request
@@ -859,6 +867,8 @@
   rules:
     - <<: *if-not-canonical-namespace
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-targeting-stable-branch
     - <<: *if-ruby2-branch
     - <<: *if-merge-request-labels-run-review-app
@@ -954,6 +964,8 @@
 ######################
 .dev-fixtures:rules:ee-and-foss:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
@@ -961,6 +973,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
@@ -1006,6 +1020,8 @@
   rules:
     # The `glfm-verify` job has dependencies on EE, so only run it for EE
     - !reference [".strict-ee-only-rules", rules]
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     # If any of the files that are DIRECTLY related to generating or managing the GLFM specification change,
     # run `glfm-verify` to get quick feedback on any needed updates, even if the MR is not yet approved
     - changes: *glfm-patterns
@@ -1032,7 +1048,6 @@
 ##################
 # Frontend rules #
 ##################
-
 .frontend:rules:predictive-default-rules:
   rules:
     - <<: *if-merge-request-approved
@@ -1041,11 +1056,15 @@
       when: never
     - <<: *if-security-merge-request
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
 
 .frontend:rules:compile-production-assets:
   rules:
     - <<: *if-not-canonical-namespace
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-targeting-stable-branch
     - <<: *if-merge-request-labels-run-review-app
     - <<: *if-merge-request-labels-run-all-e2e
@@ -1064,8 +1083,6 @@
       when: never
     - <<: *if-not-ee
       when: never
-    - <<: *if-merge-request-labels-pipeline-expedite
-      when: never
     - !reference [.frontend:rules:compile-production-assets, rules]
 
 .frontend:rules:compile-test-assets:
@@ -1092,6 +1109,8 @@
 
 .frontend:rules:default-frontend-jobs:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request-labels-frontend-and-feature-flag
     - <<: *if-default-refs
@@ -1100,6 +1119,8 @@
 .frontend:rules:default-frontend-jobs-as-if-foss:
   rules:
     - !reference [".strict-ee-only-rules", rules]
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-security-merge-request
       changes: *code-backstage-patterns
     - <<: *if-merge-request-labels-as-if-foss
@@ -1136,6 +1157,8 @@
 
 .frontend:rules:jest:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-fork-merge-request
       when: never
     - <<: *if-merge-request-labels-run-all-jest
@@ -1175,6 +1198,8 @@
   rules:
     - !reference [".strict-ee-only-rules", rules]
     - <<: *if-merge-request-labels-as-if-foss
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-jest
     - <<: *if-merge-request
       changes: *frontend-dependency-patterns
@@ -1205,6 +1230,8 @@
   rules:
     - !reference [".strict-ee-only-rules", rules]
     - <<: *if-merge-request-labels-as-if-foss
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *frontend-patterns-for-as-if-foss
 
@@ -1223,6 +1250,8 @@
   rules:
     - <<: *if-not-canonical-namespace
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-branch-refs
       changes: *frontend-build-patterns
       allow_failure: true
@@ -1235,6 +1264,8 @@
 ################
 .memory:rules:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-patterns
 
@@ -1295,6 +1326,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-targeting-stable-branch
       allow_failure: true
     - <<: *if-dot-com-gitlab-org-and-security-merge-request
@@ -1431,6 +1464,8 @@
 .rails:rules:single-db:
   rules:
     - <<: *if-merge-request-labels-run-single-db
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *db-patterns
     - <<: *if-merge-request
@@ -1440,6 +1475,8 @@
 .rails:rules:db:check-migrations-single-db:
   rules:
     - <<: *if-merge-request-labels-run-single-db
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *db-patterns
     - <<: *if-merge-request
@@ -1448,6 +1485,8 @@
 .rails:rules:single-db-ci-connection:
   rules:
     - <<: *if-merge-request-labels-run-single-db
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *db-patterns
     - <<: *if-merge-request
@@ -1457,6 +1496,8 @@
 .rails:rules:db:check-migrations-single-db-ci-connection:
   rules:
     - <<: *if-merge-request-labels-run-single-db
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *db-patterns
     - <<: *if-merge-request
@@ -1464,6 +1505,8 @@
 
 .rails:rules:db-backup:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-default-refs
       changes: *db-backup-patterns
@@ -1490,6 +1533,8 @@
   rules:
     - <<: *if-fork-merge-request
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
@@ -1504,6 +1549,8 @@
 
 .rails:rules:rspec-predictive:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-approved
       when: never
     - <<: *if-automated-merge-request
@@ -1523,6 +1570,8 @@
 
 .rails:rules:ee-and-foss-mr-with-migration:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request
       changes: *db-patterns
     - <<: *if-merge-request-labels-run-all-rspec
@@ -1579,6 +1628,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
@@ -1635,6 +1686,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *core-backend-patterns
@@ -1661,6 +1714,8 @@
       when: never
     - <<: *if-fork-merge-request
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - !reference [".rails:rules:ee-and-foss-default-rules", rules]
     - <<: *if-merge-request-labels-as-if-foss
       changes: *backend-patterns
@@ -1671,6 +1726,8 @@
       when: never
     - <<: *if-fork-merge-request
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - !reference [".rails:rules:ee-and-foss-default-rules", rules]
     - <<: *if-merge-request-labels-as-if-foss
       changes: *backend-patterns
@@ -1681,12 +1738,16 @@
       when: never
     - <<: *if-fork-merge-request
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - !reference [".rails:rules:system-default-rules", rules]
     - <<: *if-merge-request-labels-as-if-foss
       changes: *code-backstage-patterns
 
 .rails:rules:ee-and-foss-db-library-code:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *db-library-patterns
     - <<: *if-merge-request-labels-run-all-rspec
@@ -1696,6 +1757,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-merge-request-labels-run-all-rspec
     - <<: *if-merge-request
       changes: *code-backstage-patterns
@@ -1724,6 +1787,8 @@
       when: never
     - <<: *if-merge-request-labels-as-if-foss
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-security-merge-request
       changes: *code-backstage-patterns
     - <<: *if-dot-com-gitlab-org-merge-request
@@ -1753,6 +1818,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-branch-schedule-nightly
     - <<: *if-ruby2-branch-schedule-nightly
     - <<: *if-merge-request-labels-run-all-rspec
@@ -1791,6 +1858,8 @@
 
 .rails:rules:default-branch-schedule-nightly--code-backstage-default-rules:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-branch-schedule-nightly
     - <<: *if-merge-request
       changes: [".gitlab/ci/rails.gitlab-ci.yml"]
@@ -1809,6 +1878,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
@@ -2025,6 +2096,8 @@
 #################
 .reports:rules:code_quality:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$CODE_QUALITY_DISABLED'
       when: never
     # Run code_quality on master until https://gitlab.com/gitlab-org/gitlab/-/issues/363747 is resolved
@@ -2036,6 +2109,8 @@
 
 .reports:rules:brakeman-sast:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: $SAST_DISABLED
       when: never
     - if: $SAST_EXCLUDED_ANALYZERS =~ /brakeman/
@@ -2047,6 +2122,8 @@
 
 .reports:rules:semgrep-sast:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: $SAST_DISABLED
       when: never
     - if: $SAST_EXCLUDED_ANALYZERS =~ /semgrep/
@@ -2064,6 +2141,8 @@
 
 .reports:rules:secret_detection:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$SECRET_DETECTION_DISABLED'
       when: never
     # Scan each commit on master to feed the Vulnerability Reports with detected secrets
@@ -2073,6 +2152,8 @@
 
 .reports:rules:gemnasium-dependency_scanning:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$DEPENDENCY_SCANNING_DISABLED || $GITLAB_FEATURES !~ /\bdependency_scanning\b/ || $DS_EXCLUDED_ANALYZERS =~ /gemnasium([^-]|$)/'
       when: never
     # Run Dependency Scanning on master until https://gitlab.com/gitlab-org/gitlab/-/issues/361657 is resolved
@@ -2082,6 +2163,8 @@
 
 .reports:rules:gemnasium-python-dependency_scanning:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$DEPENDENCY_SCANNING_DISABLED || $GITLAB_FEATURES !~ /\bdependency_scanning\b/ || $DS_EXCLUDED_ANALYZERS =~ /gemnasium-python/'
       when: never
     # Run Dependency Scanning on master until https://gitlab.com/gitlab-org/gitlab/-/issues/361657 is resolved
@@ -2091,6 +2174,8 @@
 
 .reports:rules:yarn-audit-dependency_scanning:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$DEPENDENCY_SCANNING_DISABLED || $GITLAB_FEATURES !~ /\bdependency_scanning\b/'
       when: never
     # Run Dependency Scanning on master until https://gitlab.com/gitlab-org/gitlab/-/issues/361657 is resolved
@@ -2100,6 +2185,8 @@
 
 .reports:rules:test-dast:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - if: '$DAST_DISABLED || $GITLAB_FEATURES !~ /\bdast\b/'
       when: never
     - <<: *if-merge-request
@@ -2281,6 +2368,8 @@
 
 .setup:rules:gitlab_git_test:
   rules:
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
@@ -2311,6 +2400,8 @@
   rules:
     - <<: *if-not-ee
       when: never
+    - <<: *if-merge-request-labels-pipeline-expedite
+      when: never
     - <<: *if-default-refs
       changes: *code-backstage-patterns
 
diff --git a/.gitlab/issue_templates/AI Project Proposal.md b/.gitlab/issue_templates/AI Project Proposal.md
index 1b3202b4028..94c4dbdeca1 100644
--- a/.gitlab/issue_templates/AI Project Proposal.md
+++ b/.gitlab/issue_templates/AI Project Proposal.md
@@ -1,8 +1,18 @@
-<!-- AI Project Proposal title format: 🤖 [AI Proposal] {`Need/outcome` } + {`Beneficiary`} + {`Job/Small Job`}
+<!--
+HOW TO USE THIS TEMPLATE
+To propose an AI experiment, focus on completing the “Experiment” section first. As you refine the idea and gather feedback on your experiment, use the “Feature release” section to define how it will evolve as a Beta or GA capability. It's important that we link experiment to feature release. Feel free to add sections, but keep the existing ones.
 
-The title should be something that is easily understood that quickly communicates the intent of the project allowing team members to easily understand and recognize the expected work that will be done.
+You can choose how to get started with this template. For example, the proposal can start as an issue, and then be promoted to an epic to house all the work related to the experiment/prototype and feature release. If you prefer to start with an epic, you have to manually apply the proposal template. Regardless, if the experiment is eventually prioritized for development, the template content will need to appear in a top-level epic so it can be tracked alongside other prioritized AI experiments.
 
-A proposal title should combine the beneficiary of the feature/UI, the job it will allow them to accomplish, and their expected outcome when the work is delivered. Well-defined statements are concise without sacrificing the substance of the proposal so that anyone can understand it at a glance. (e.g.🤖 {Reduce the effort} + {for security teams} + {when prioritizing business-critical risks in their assets}) -->
+TITLE FORMAT
+🤖 [AI Proposal] {Need/outcome} {Beneficiary} {Job/Small Job}
+
+The title should be something that is easily understood that quickly communicates the intent of the project allowing team members to easily understand and recognize the expected work that will be done. A proposal title should combine the beneficiary of the feature/UI, the job it will allow them to accomplish (see https://about.gitlab.com/handbook/product/ux/jobs-to-be-done/#how-to-write-a-jtbd), and their expected outcome when the work is delivered. Well-defined statements are concise without sacrificing the substance of the proposal so that anyone can understand it at a glance. (e.g. {Reduce the effort} {for security teams} {when prioritizing business-critical risks in their assets}).
+-->
+
+# Experiment
+
+This section should be completed prior to work on the Experiment beginning.
 
 # [Experiment](https://docs.gitlab.com/ee/policy/alpha-beta-support.html#experiment)
 
@@ -21,19 +31,22 @@ _What assumptions are you making about this problem and the solution?_
 _What [personas](https://about.gitlab.com/handbook/product/personas/#list-of-user-personas) have this problem, who is the intended user?_
 
 ## Proposal
-<!-- Use this section to explain the proposed changes, including details around usage and business drivers. -->
+<!-- Explain the proposed changes, including details around usage and business drivers. -->
 
 ### Success
 _How will you measure whether this experiment is a success?_
 
-# [General Availability](https://docs.gitlab.com/ee/policy/alpha-beta-support.html#generally-available-ga)
 
-## Main Job story
+# Feature release
+<!-- DO NOT REMOVE THIS SECTION
+Although the initial focus is on the “Experiment” section, do not remove this “Feature release” section. It's important that we link experiment to feature release. Fill this section as you progress.
+-->
+### Main Job story
 _What job to be done will this solve?_
 <!-- What is the [Main Job story](https://about.gitlab.com/handbook/product/ux/jobs-to-be-done/#how-to-write-a-jtbd) that this proposal was derived from? (e.g. When I am on triage rotation, I want to address all the business-critical risks in my assets, So I can minimize the likelihood of my organization being compromised by a security breach.) -->
 
-### Proposal updates/additions
-<!-- Use this section to explain any changes or updates to the original proposal, including details around usage, business drivers, and reasonings that drove the updates/additions. -->
+## Proposal updates/additions
+<!-- Explain any changes or updates to the original proposal from the experiment, including details around usage, business drivers, and reasonings that drove the updates/additions. -->
 
 ### Problem validation
 _What validation exists that customers have this problem?_
@@ -59,34 +72,33 @@ _What tasks or actions should the user be capable of performing with this featur
 #### The user needs to be able to:
 - ...
 - ...
-- ...
 
 ## Checklist
 
 ### Experiment
-
-<details>
-<summary> Issue information </summary>
+<details> <summary> Issue information </summary>
 
 - [ ] Add information to the issue body about:
-  - [ ] The user problem being solved
-  - [ ] Your assumptions
-  - [ ] Who it's for, list of personas impacted
-  - [ ] Your proposal
+    - [ ] The user problem being solved
+    - [ ] Your assumptions
+    - [ ] Who it's for, list of personas impacted
+    - [ ] Your proposal
 - [ ] Add relevant designs to the Design Management area of the issue if available
+- [ ] Confirm that an unexpected outage of this feature will not negatively impact the application or other features
+- [ ] Add a feature flag so that this feature can be quickly disabled if/when needed
+- [ ] If this experiment introduces a new service or data store, ensure it is not processing or storing [red data](https://about.gitlab.com/handbook/security/data-classification-standard.html#data-classification-levels) without a security and if needed legal review
+  - *NOTE*: We recommend using one of the already adopted models or data stores. If you need to use something else, be aware that using other models or data stores will require additional review during the feature stage for operational fitness and compliance.
 - [ ] Ensure this issue has the ~wg-ai-integration label to ensure visibility to various teams working on this
 
 </details>
 
-### General Availability
-
-<details>
-<summary>Issue information</summary>
+### Feature release
+<details> <summary> Issue information </summary>
 
 - [ ] Add information to the issue body about:
-  - [ ] Your proposal
-  - [ ]  The Job Statement it's expected to satisfy
-  - [ ] Details about the user problem and provide any research or problem validation
+    - [ ] Your proposal
+    - [ ] The Job Statement it's expected to satisfy
+    - [ ] Details about the user problem and provide any research or problem validation
     - [ ] List the personas impacted by the proposal.
 - [ ] Add all relevant solution validation issues to the Linked items section that shows this proposal will solve the customer problem, or details explaining why it's not possible to provide that validation.
 - [ ] Add relevant designs to the Design Management area of the issue.
@@ -95,30 +107,27 @@ _What tasks or actions should the user be capable of performing with this featur
 
 </details>
 
-<details>
-<summary>Technical needs</summary>
+<details> <summary> Technical needs </summary>
 
-- [ ] [Operational Requirements Review - Checklist - #note_1337519985](https://gitlab.com/gitlab-org/gitlab/-/issues/403859#note_1337519985)
+- [ ] Please consider the operational aspects of the feature you are creating. A list of things to think about is in: https://gitlab.com/gitlab-org/gitlab/-/issues/403859. We will be improving this process in the future: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117637#note_1353253349. 
 
-1. **Work estimate and skills needs to build an ML viable feature:** To build any ML feature depending on the work, there are many personas that contribute including, Data Scientist, NLP engineer, ML Engineer, MLOps Engineer, ML Infra engineers, and Fullstack engineer to integrate the ML Services with Gitlab. Post-prototype we would assess the skills needed to build a production-grade ML feature for the prototype
-2. **Data Limitation:** We would like to upfront validate if we have viable data for the feature including whether we can use the DataOps pipeline of ModelOps or create a custom one. We would want to understand the training data, test data, and feedback data to dial up the accuracy and the limitations of the data.
-3. **Model Limitation:** We would want to understand if we can use an open-source pre-trained model, tune and customize it or start a  model from scratch as well. Further, we would asses based on the ModelOps model evaluation framework which would be the right model to use based on the use case.
-4. **Cost, Scalability, Reliability:** We would want to estimate the cost of hosting, serving, inference of the model, and the full end-to-end infrastructure including monitoring and observability.
-5. **Legal and Ethical Framework:** We would want to align with legal and ethical framework like any other ModelOps features to cover across the nine principles of responsible ML and any legal support needed.
+1. Work estimate and skills needs to build an ML viable feature: To build any ML feature depending on the work, there are many personas that contribute including, Data Scientist, NLP engineer, ML Engineer, MLOps Engineer, ML Infra engineers, and Fullstack engineer to integrate the ML Services with Gitlab. Post-prototype we would assess the skills needed to build a production-grade ML feature for the prototype.
+2. Data Limitation: We would like to upfront validate if we have viable data for the feature including whether we can use the DataOps pipeline of ModelOps or create a custom one. We would want to understand the training data, test data, and feedback data to dial up the accuracy and the limitations of the data.
+3. Model Limitation: We would want to understand if we can use an open-source pre-trained model, tune and customize it or start a model from scratch as well. Further, we would assess based on the ModelOps model evaluation framework which would be the right model to use based on the use case.
+4. Cost, Scalability, Reliability: We would want to estimate the cost of hosting, serving, inference of the model, and the full end-to-end infrastructure including monitoring and observability.
+5. Legal and Ethical Framework: We would want to align with legal and ethical framework like any other ModelOps features to cover across the nine principles of responsible ML and any legal support needed.
 
 </details>
 
-<details>
-<summary>Dependency needs</summary>
+<details> <summary> Dependency needs </summary>
 
-- [ ] [Operational Requirements Review - Checklist - #note_1337519985](https://gitlab.com/gitlab-org/gitlab/-/issues/403859#note_1337519985)
+- [ ] Please consider the operational aspects of the service you are creating. A list of things to think about is in: https://gitlab.com/gitlab-org/gitlab/-/issues/403859. We will be improving this process in the future: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/117637#note_1353253349. 
 
 </details>
 
-<details>
-<summary>Legal needs</summary>
+<details> <summary> Legal needs </summary>
 
-- [ ] TBD
+- [ ]  TBD
 
 </details>
 
@@ -134,5 +143,3 @@ _What tasks or actions should the user be capable of performing with this featur
 /label ~wg-ai-integration
 /cc @tmccaslin @hbenson @wayne @pedroms @jmandell
 /confidential
-
-[Make change to this template](https://gitlab.com/gitlab-org/gitlab/-/blob/master/.gitlab/issue_templates/AI%20Project%20Proposal.md)