Pluralize DevOps Report to DevOps Reports

DevOps Report (singular) actually refers to 2 features. That has caused
confusion. This changes it to be DevOps Reports (plural) in the UI, to
indicate it is a category. This aligns the app with the marketing
content, which already uses the plural version.

This also fixes some references to DevOps Report that should be
references to DevOps Adoption or DevOps Score.

Changelog: changed

app/assets/javascripts/analytics/devops_report/constants.js

@@ -2,10 +2,10 @@ import { __ } from '~/locale';
 
 export const INTRO_COOKIE_KEY = 'dev_ops_report_intro_callout_dismissed';
 
-export const INTRO_BANNER_TITLE = __('Introducing Your DevOps Report');
+export const INTRO_BANNER_TITLE = __('Introducing Your DevOps Reports');
 
 export const INTRO_BANNER_BODY = __(
-  'Your DevOps Report gives an overview of how you are using GitLab from a feature perspective. Use it to view how you compare with other organizations.',
+  'Your DevOps Reports give an overview of how you are using GitLab from a feature perspective. Use them to view how you compare with other organizations, and how your teams compare against each other.',
 );
 
 export const INTRO_BANNER_ACTION_TEXT = __('Read more');

app/views/admin/dev_ops_report/show.html.haml

-- page_title _('DevOps Report')
+- page_title _('DevOps Reports')
 - add_page_specific_style 'page_bundles/dev_ops_report'
 
 .container

app/views/layouts/nav/sidebar/_admin.html.haml

@@ -66,9 +66,9 @@
                 = _('Analytics')
           %li.divider.fly-out-top-item
           = nav_link(controller: :dev_ops_report) do
-            = link_to admin_dev_ops_report_path, title: _('DevOps Report') do
+            = link_to admin_dev_ops_report_path, title: _('DevOps Reports') do
               %span
-                = _('DevOps Report')
+                = _('DevOps Reports')
           = nav_link(controller: :usage_trends) do
             = link_to admin_usage_trends_path, title: _('Usage Trends') do
               %span

doc/development/contributing/issue_workflow.md

@@ -168,7 +168,7 @@ their color is `#428BCA`.
 `<Category Name>` is the category name as it is in the single source of truth for categories at
 <https://gitlab.com/gitlab-com/www-gitlab-com/blob/master/data/categories.yml>.
 
-For instance, the "DevOps Report" category is represented by the
+For instance, the "DevOps Reports" category is represented by the
 ~"Category:DevOps Reports" label in the `gitlab-org` group since its
 `devops_reports.name` value is "DevOps Reports".
 

doc/development/service_ping/index.md

@@ -55,7 +55,7 @@ We use the following terminology to describe the Service Ping components:
 
 - The main purpose of Service Ping is to build a better GitLab. Data about how GitLab is used is collected to better understand feature/stage adoption and usage, which helps us understand how GitLab is adding value and helps our team better understand the reasons why people use GitLab and with this knowledge we're able to make better product decisions.
 - As a benefit of having Service Ping active, GitLab lets you analyze the users' activities over time of your GitLab installation.
-- As a benefit of having Service Ping active, GitLab provides you with The DevOps Report,which gives you an overview of your entire instance's adoption of Concurrent DevOps from planning to monitoring.
+- As a benefit of having Service Ping active, GitLab provides you with [DevOps Score](../../user/admin_area/analytics/dev_ops_report.md#devops-score), which gives you an overview of your entire instance's adoption of Concurrent DevOps from planning to monitoring.
 - You get better, more proactive support. (assuming that our TAMs and support organization used the data to deliver more value)
 - You get insight and advice into how to get the most value out of your investment in GitLab. Wouldn't you want to know that a number of features or values are not being adopted in your organization?
 - You get a report that illustrates how you compare against other similar organizations (anonymized), with specific advice and recommendations on how to improve your DevOps processes.
@@ -186,7 +186,7 @@ sequenceDiagram
     S3 Bucket->>Snowflake DW: Import data
     Snowflake DW->>Snowflake DW: Transform data using dbt
     Snowflake DW->>Sisense Dashboards: Data available for querying
-    Versions Application->>GitLab Instance: DevOps Report (Conversational Development Index)
+    Versions Application->>GitLab Instance: DevOps Score (Conversational Development Index)
 ```
 
 ## How Service Ping works

doc/user/admin_area/analytics/dev_ops_report.md

@@ -4,21 +4,21 @@ group: Optimize
 info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/engineering/ux/technical-writing/#assignments
 ---
 
-# DevOps Report **(FREE SELF)**
+# DevOps Reports **(FREE SELF)**
 
-> [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/20976) from Conversational Development Index in GitLab 12.6.
-
-The DevOps Report gives you an overview of your entire instance's adoption of
+DevOps Reports give you an overview of your entire instance's adoption of
 [Concurrent DevOps](https://about.gitlab.com/topics/concurrent-devops/)
 from planning to monitoring.
 
-To see DevOps Report:
+To see DevOps Reports:
 
 1. On the top bar, select **Menu > Admin**.
-1. On the left sidebar, select **Analytics > DevOps Report**.
+1. On the left sidebar, select **Analytics > DevOps Reports**.
 
 ## DevOps Score
 
+> [Renamed](https://gitlab.com/gitlab-org/gitlab/-/issues/20976) from Conversational Development Index in GitLab 12.6.
+
 NOTE:
 To see the DevOps score, you must activate your GitLab instance's [Service Ping](../settings/usage_statistics.md#service-ping). This is because DevOps Score is a comparative tool, so your score data must be centrally processed by GitLab Inc. first.
 
@@ -72,4 +72,4 @@ DevOps Adoption allows you to:
 - Identify specific groups that are lagging in their adoption of GitLab, so you can help them along in their DevOps journey.
 - Find the groups that have adopted certain features, and can provide guidance to other groups on how to use those features.
 
-![DevOps Report](img/admin_devops_adoption_v14_2.png)
+![DevOps Adoption](img/admin_devops_adoption_v14_2.png)

doc/user/admin_area/analytics/index.md

@@ -15,5 +15,5 @@ Administrators have access to instance-wide analytics:
 
 There are several kinds of statistics:
 
-- [DevOps Report](dev_ops_report.md): Provides an overview of your entire instance's feature usage.
+- [DevOps Reports](dev_ops_report.md): Provides an overview of your entire instance's feature usage.
 - [Usage Trends](usage_trends.md): Shows how much data your instance contains, and how that is changing.

doc/user/group/devops_adoption/index.md

@@ -48,7 +48,7 @@ With DevOps Adoption you can:
 - Identify specific subgroups that are lagging in their adoption of GitLab, so you can help them along in their DevOps journey.
 - Find the subgroups that have adopted certain features, and can provide guidance to other subgroups on how to use those features.
 
-![DevOps Report](img/group_devops_adoption_v14_2.png)
+![DevOps Adoption](img/group_devops_adoption_v14_2.png)
 
 Feature adoption is based on usage in the previous calendar month. Data is updated on the first day
 of each month. If the monthly update fails, it tries again daily until successful.

ee/app/views/admin/dev_ops_report/_devops_tabs.html.haml

 - service_ping_enabled = Gitlab::CurrentSettings.usage_ping_enabled
 
 %h2
-  = _('DevOps Report')
+  = _('DevOps Reports')
 
 - if !service_ping_enabled
   #js-devops-service-ping-disabled{ data: { is_admin: current_user&.admin.to_s, empty_state_svg_path: image_path('illustrations/convdev/convdev_no_index.svg'), enable_service_ping_path: metrics_and_profiling_admin_application_settings_path(anchor: 'js-usage-settings') } }

locale/gitlab.pot

@@ -11780,7 +11780,7 @@ msgstr ""
 msgid "DevOps Adoption"
 msgstr ""
 
-msgid "DevOps Report"
+msgid "DevOps Reports"
 msgstr ""
 
 msgid "DevOps adoption"
@@ -18644,7 +18644,7 @@ msgstr ""
 msgid "Interval Pattern"
 msgstr ""
 
-msgid "Introducing Your DevOps Report"
+msgid "Introducing Your DevOps Reports"
 msgstr ""
 
 msgid "Invalid Insights config file detected"
@@ -39618,7 +39618,7 @@ msgstr ""
 msgid "Your CSV import for project"
 msgstr ""
 
-msgid "Your DevOps Report gives an overview of how you are using GitLab from a feature perspective. Use it to view how you compare with other organizations."
+msgid "Your DevOps Reports give an overview of how you are using GitLab from a feature perspective. Use them to view how you compare with other organizations, and how your teams compare against each other."
 msgstr ""
 
 msgid "Your GPG keys (%{count})"