Merge branch 'mw-rename-devops-score-to-devops-report' into 'master'

Rename DevOps Score in the product to DevOps Report

See merge request gitlab-org/gitlab!39953

app/views/admin/dev_ops_score/_callout.html.haml

@@ -2,12 +2,12 @@
 .user-callout{ data: { uid: 'dev_ops_score_intro_callout_dismissed' } }
   .bordered-box.landing.content-block
     %button.btn.btn-default.close.js-close-callout{ type: 'button',
-      'aria-label' => _('Dismiss DevOps Score introduction') }
+      'aria-label' => _('Dismiss DevOps Report introduction') }
       = icon('times', class: 'dismiss-icon', 'aria-hidden' => 'true')
     .user-callout-copy
       %h4
-        = _('Introducing Your DevOps Score')
+        = _('Introducing Your DevOps Report')
       %p
-        = _('Your DevOps Score gives an overview of how you are using GitLab from a feature perspective. View how you compare with other organizations, discover features you are not using, and learn best practices through blog posts and white papers.')
+        = _('Your DevOps Report gives an overview of how you are using GitLab from a feature perspective. View how you compare with other organizations, discover features you are not using, and learn best practices through blog posts and white papers.')
     .svg-container.devops
       = custom_icon('dev_ops_score_overview')

app/views/admin/dev_ops_score/_no_data.html.haml

@@ -4,4 +4,4 @@
     %h4= _('Data is still calculating...')
     %p
       = _('In order to gather accurate feature usage data, it can take 1 to 2 weeks to see your index.')
-      = link_to _('Learn more'), help_page_path('user/admin_area/analytics/dev_ops_score'), target: '_blank'
+      = link_to _('Learn more'), help_page_path('user/admin_area/analytics/dev_ops_report'), target: '_blank'

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

-- page_title _('DevOps Score')
+- page_title _('DevOps Report')
 - usage_ping_enabled = Gitlab::CurrentSettings.usage_ping_enabled
 
 .container
@@ -16,10 +16,10 @@
         %h2.devops-header-title{ class: "devops-#{score_level(@metric.average_percentage_score)}-score" }
           = number_to_percentage(@metric.average_percentage_score, precision: 1)
         .devops-header-subtitle
-          = _('index')
+          = _('DevOps')
           %br
-          = _('score')
-          = link_to icon('question-circle', 'aria-hidden' => 'true'), help_page_path('user/admin_area/analytics/dev_ops_score')
+          = _('Score')
+          = link_to icon('question-circle', 'aria-hidden' => 'true'), help_page_path('user/admin_area/analytics/dev_ops_report')
 
       .devops-cards.board-card-container
         - @metric.cards.each do |card|

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

@@ -62,9 +62,9 @@
                 = _('Analytics')
           %li.divider.fly-out-top-item
           = nav_link(controller: :dev_ops_score) do
-            = link_to admin_dev_ops_score_path, title: _('DevOps Score') do
+            = link_to admin_dev_ops_score_path, title: _('DevOps Report') do
               %span
-                = _('DevOps Score')
+                = _('DevOps Report')
           = nav_link(controller: :cohorts) do
             = link_to admin_cohorts_path, title: _('Cohorts') do
               %span

changelogs/unreleased/mw-rename-devops-score-to-devops-report.yml

+---
+title: Rename DevOps Score to DevOps Report
+merge_request: 39953
+author:
+type: changed

doc/development/contributing/issue_workflow.md

@@ -43,7 +43,7 @@ Most issues will have labels for at least one of the following:
 - Type: `~feature`, `~bug`, `~tooling`, `~documentation`, etc.
 - Stage: `~"devops::plan"`, `~"devops::create"`, etc.
 - Group: `~"group::source code"`, `~"group::knowledge"`, `~"group::editor"`, etc.
-- Category: `~"Category:Code Analytics"`, `~"Category:DevOps Score"`, `~"Category:Templates"`, etc.
+- Category: `~"Category:Code Analytics"`, `~"Category:DevOps Reports"`, `~"Category:Templates"`, etc.
 - Feature: `~wiki`, `~ldap`, `~api`, `~issues`, `~"merge requests"`, etc.
 - Department: `~UX`, `~Quality`
 - Team: `~"Technical Writing"`, `~Delivery`
@@ -188,9 +188,9 @@ 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 Score" category is represented by the
-~"Category:DevOps Score" label in the `gitlab-org` group since its
-`devops_score.name` value is "DevOps Score".
+For instance, the "DevOps Report" category is represented by the
+~"Category:DevOps Reports" label in the `gitlab-org` group since its
+`devops_score.name` value is "DevOps Reports".
 
 If a category's label doesn't respect this naming convention, it should be specified
 with [the `label` attribute](https://about.gitlab.com/handbook/marketing/website/#category-attributes)

doc/development/telemetry/usage_ping.md

@@ -37,7 +37,7 @@ More useful links:
 
 - The main purpose of Usage 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 the usage ping active, GitLab lets you analyze the users’ activities over time of your GitLab installation.
-- As a benefit of having the usage ping active, GitLab provides you with The DevOps Score,which gives you an overview of your entire instance’s adoption of Concurrent DevOps from planning to monitoring.
+- As a benefit of having the usage 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.
 - You will get better, more proactive support. (assuming that our TAMs and support organization used the data to deliver more value)
 - You will 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.
@@ -108,7 +108,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 Score (Conversational Development Index)
+    Versions Application->>GitLab Instance: DevOps Report (Conversational Development Index)
 ```
 
 ## How Usage Ping works

doc/user/admin_area/analytics/convdev.md

 ---
-redirect_to: 'dev_ops_score.md'
+redirect_to: 'dev_ops_report.md'
 ---
 
-This document was moved to [another location](dev_ops_score.md).
+This document was moved to [another location](dev_ops_report.md).

doc/user/admin_area/analytics/dev_ops_score.md → doc/user/admin_area/analytics/dev_ops_report.md

-# DevOps Score
+# DevOps Report
 
 > - [Introduced](https://gitlab.com/gitlab-org/gitlab-foss/-/issues/30469) in GitLab 9.3.
 > - [Renamed from Conversational Development Index](https://gitlab.com/gitlab-org/gitlab/-/issues/20976) in GitLab 12.6.
@@ -6,7 +6,7 @@
 NOTE: **Note:**
 Your GitLab instance's [usage ping](../settings/usage_statistics.md#usage-ping-core-only) must be activated in order to use this feature.
 
-The DevOps Score gives you an overview of your entire instance's adoption of
+The DevOps Report gives you an overview of your entire instance's adoption of
 [Concurrent DevOps](https://about.gitlab.com/topics/concurrent-devops/)
 from planning to monitoring.
 
@@ -15,9 +15,9 @@ the last 30 days, averaged over the number of active users in that time period.
 provides a Lead score per feature, which is calculated based on GitLab's analysis
 of top-performing instances based on [usage ping data](../settings/usage_statistics.md#usage-ping-core-only) that GitLab has
 collected. Your score is compared to the lead score of each feature and then expressed as a percentage at the bottom of said feature.
-Your overall **index score** is an average of your feature scores. You can use this score to compare your DevOps status to other organizations.
+Your overall **DevOps Score** is an average of your feature scores. You can use this score to compare your DevOps status to other organizations.
 
-![DevOps Score](img/dev_ops_score_v12_6.png)
+![DevOps Report](img/dev_ops_report_v13_4.png)
 
 The page also provides helpful links to articles and GitLab docs, to help you
 improve your scores.

doc/user/admin_area/analytics/index.md

@@ -6,5 +6,5 @@ Administrators have access to instance-wide analytics, as shown in **Admin Area
 
 There are two kinds of statistics:
 
-- [Dev Ops Score](dev_ops_score.md): Provides an overview of your entire instance's feature usage.
+- [DevOps Report](dev_ops_report.md): Provides an overview of your entire instance's feature usage.
 - [User Cohorts](user_cohorts.md): Display the monthly cohorts of new users and their activities over time.

doc/user/admin_area/monitoring/convdev.md

 ---
-redirect_to: '../analytics/dev_ops_score.md'
+redirect_to: '../analytics/dev_ops_report.md'
 ---
 
-Conversational Development Index was renamed to [DevOps Score](../analytics/dev_ops_score.md) in GitLab 12.6.
+Conversational Development Index was renamed to [DevOps Report](../analytics/dev_ops_report.md) in GitLab 12.6.

doc/user/admin_area/monitoring/dev_ops_score.md → doc/user/admin_area/monitoring/dev_ops_report.md

 ---
-redirect_to: '../analytics/dev_ops_score.md'
+redirect_to: '../analytics/dev_ops_report.md'
 ---
 
-This document was moved to [another location](../analytics/dev_ops_score.md).
+This document was moved to [another location](../analytics/dev_ops_report.md).

locale/gitlab.pot

@@ -8583,7 +8583,10 @@ msgstr ""
 msgid "Detect host keys"
 msgstr ""
 
-msgid "DevOps Score"
+msgid "DevOps"
+msgstr ""
+
+msgid "DevOps Report"
 msgstr ""
 
 msgid "Diff content limits"
@@ -8729,7 +8732,7 @@ msgid_plural "Dismiss %d selected vulnerabilities as"
 msgstr[0] ""
 msgstr[1] ""
 
-msgid "Dismiss DevOps Score introduction"
+msgid "Dismiss DevOps Report introduction"
 msgstr ""
 
 msgid "Dismiss Merge Request promotion"
@@ -13318,7 +13321,7 @@ msgstr ""
 msgid "Introducing Value Stream Analytics"
 msgstr ""
 
-msgid "Introducing Your DevOps Score"
+msgid "Introducing Your DevOps Report"
 msgstr ""
 
 msgid "Invalid Git ref"
@@ -21469,6 +21472,9 @@ msgstr ""
 msgid "Scopes can't be blank"
 msgstr ""
 
+msgid "Score"
+msgstr ""
+
 msgid "Scroll down"
 msgstr ""
 
@@ -28572,7 +28578,7 @@ msgstr ""
 msgid "Your Default Notification Email will be used for account notifications if a %{openingTag}group-specific email address%{closingTag} is not set."
 msgstr ""
 
-msgid "Your DevOps Score gives an overview of how you are using GitLab from a feature perspective. View how you compare with other organizations, discover features you are not using, and learn best practices through blog posts and white papers."
+msgid "Your DevOps Report gives an overview of how you are using GitLab from a feature perspective. View how you compare with other organizations, discover features you are not using, and learn best practices through blog posts and white papers."
 msgstr ""
 
 msgid "Your GPG keys (%{count})"
@@ -29323,9 +29329,6 @@ msgstr ""
 msgid "in project %{link_to_project}"
 msgstr ""
 
-msgid "index"
-msgstr ""
-
 msgid "instance completed"
 msgid_plural "instances completed"
 msgstr[0] ""
@@ -29997,9 +30000,6 @@ msgstr ""
 msgid "satisfied"
 msgstr ""
 
-msgid "score"
-msgstr ""
-
 msgid "security Reports|There was an error creating the merge request"
 msgstr ""
 

spec/features/admin/admin_dev_ops_score_spec.rb

@@ -2,7 +2,7 @@
 
 require 'spec_helper'
 
-RSpec.describe 'DevOps Score page' do
+RSpec.describe 'DevOps Report page' do
   before do
     sign_in(create(:admin))
   end
@@ -10,11 +10,11 @@ RSpec.describe 'DevOps Score page' do
   it 'has dismissable intro callout', :js do
     visit admin_dev_ops_score_path
 
-    expect(page).to have_content 'Introducing Your DevOps Score'
+    expect(page).to have_content 'Introducing Your DevOps Report'
 
     find('.js-close-callout').click
 
-    expect(page).not_to have_content 'Introducing Your DevOps Score'
+    expect(page).not_to have_content 'Introducing Your DevOps Report'
   end
 
   context 'when usage ping is disabled' do
@@ -31,7 +31,7 @@ RSpec.describe 'DevOps Score page' do
     it 'hides the intro callout' do
       visit admin_dev_ops_score_path
 
-      expect(page).not_to have_content 'Introducing Your DevOps Score'
+      expect(page).not_to have_content 'Introducing Your DevOps Report'
     end
   end
 

spec/services/submit_usage_ping_service_spec.rb

@@ -68,7 +68,7 @@ RSpec.describe SubmitUsagePingService do
     end
   end
 
-  shared_examples 'saves DevOps score data from the response' do
+  shared_examples 'saves DevOps report data from the response' do
     it do
       expect { subject.execute }
         .to change { DevOpsScore::Metric.count }
@@ -123,15 +123,15 @@ RSpec.describe SubmitUsagePingService do
         stub_response(body: with_conv_index_params)
       end
 
-      it_behaves_like 'saves DevOps score data from the response'
+      it_behaves_like 'saves DevOps report data from the response'
     end
 
-    context 'when DevOps score data is passed' do
+    context 'when DevOps report data is passed' do
       before do
         stub_response(body: with_dev_ops_score_params)
       end
 
-      it_behaves_like 'saves DevOps score data from the response'
+      it_behaves_like 'saves DevOps report data from the response'
     end
 
     context 'with save_raw_usage_data feature enabled' do