Add custom copy for each empty stage

app/assets/javascripts/cycle_analytics/cycle_analytics_bundle.js.es6

@@ -30,7 +30,7 @@ $(() => {
     components: {
       'stage-issue-component': gl.cycleAnalytics.StageIssueComponent,
       'stage-plan-component': gl.cycleAnalytics.StagePlanComponent,
-      'stage-code-component': gl .cycleAnalytics.StageCodeComponent,
+      'stage-code-component': gl.cycleAnalytics.StageCodeComponent,
       'stage-test-component': gl.cycleAnalytics.StageTestComponent,
       'stage-review-component': gl.cycleAnalytics.StageReviewComponent,
       'stage-staging-component': gl.cycleAnalytics.StageStagingComponent,

app/assets/javascripts/cycle_analytics/cycle_analytics_store.js.es6

@@ -2,6 +2,16 @@
 ((global) => {
   global.cycleAnalytics = global.cycleAnalytics || {};
 
+  const EMPTY_STAGE_TEXTS = {
+    issue: 'The issue stage shows the time it takes from creating an issue to assigning the issue to a milestone, or add the issue to a list on your Issue Board. Begin creating issues to see data for this stage.',
+    plan: 'The planning stage shows the time from the previous step to pushing your first commit. This time will be added automatically once you push your first commit.',
+    code: 'The coding stage shows the time from the first commit to creating the merge request. The data will automatically be added here once you create your first merge request.',
+    test: 'The testing stage shows the time GitLab CI takes to run every pipeline for the related merge request. The data will automatically be added after your first pipeline finishes running.',
+    review: 'The review stage shows the time from creating the merge request to merging it. The data will automatically be added after you merge your first merge request.',
+    staging: 'The staging stage shows the time between merging the MR and deploying code to the production environment. The data will be automatically added once you deploy to production for the first time.',
+    production: 'The production stage shows the total time it takes between creating an issue and deploying the code to production. The data will be automatically added once you have completed the full idea to production cycle.',
+  };
+
   global.cycleAnalytics.CycleAnalyticsStore = {
     state: {
       summary: '',
@@ -27,6 +37,7 @@
         const stageName = item.title.toLowerCase();
         item.active = false;
         item.isUserAllowed = data.permissions[stageName];
+        item.emptyStageText = EMPTY_STAGE_TEXTS[stageName];
         item.component = `stage-${stageName}-component`;
       });
       newData.analytics = data;

app/views/projects/cycle_analytics/_empty_stage.html.haml

@@ -4,9 +4,4 @@
       = custom_icon ('icon_no_data')
     %h4 We don’t have enough data to show this stage.
     %p
-      The test phase measures the median time to run the entire pipeline for that project.
-      It’s related to the time GitLab CI takes to run every job for the commits pushed
-      to that merge request defined in the previous stage.
-      Learn more about the
-      %a{ :href => "https://docs.gitlab.com/ce/user/project/cycle_analytics.html" }
-        expected workflow and calculations.
+      {{currentStage.emptyStageText}}