Insights: Inconsistent Data in Graphs

Summary

I'm seeing 4 confusing "issues":

  1. "all" merge requests shows 0 for march 2021 yet "merged" merge requests shows 1 (I realised this is because of the differend period_field- changing the merged graph to use created_at (in keeping with the other graph) leads them to marry up propery 👍
  2. #364429 (closed) "all" shows the Support average as 125m
  3. (#362895 (moved)) my cursor / mouse pointer changes when hovering over the greyscale summaries underneath the graphs (to a horizontal double headed arrow, like that used to resize possibly)- this leads me to believe perhaps the graph timeline can be moved/zoomed etc (but clicking, dragging etc has no effect) - fixed with fix(GlChart): tooltip conflicting with datazoom (gitlab-ui!2908 - merged)
  4. the greyscale summary underneath the second graph is flat. Removing the Support serie (by clicking the label) changes the "summary" to depict just the development data (ignoring the undefined data). Removing the Support and Development series changes the "summary" to depict the undefined data (screenshots below)

Update: this issue is about point 4. Points 1. and 3. has been fixed. Point 2 has a separate issue now.

Proposed solution to fix point 4. is here.

image

image

image

I may just need help understanding the graphs (i.e. user error) but perhaps there is a bug?

This is on a self hosted instance (13.9). I can post additional details/logs etc if needed.

Steps to reproduce

mergeCharts:
  title: "Charts for Merge Requests"
  charts:
    - title: "Monthly Created"
      description: "Opened per month"
      type: stacked-bar
      query:
        issuable_type: merge_request
        issuable_state: all
        collection_labels:
          - Support
          - Development
        group_by: month
        period_limit: 24
    - title: "Monthly Merged"
      description: "Merged per month"
      type: stacked-bar
      query:
        issuable_type: merge_request
        issuable_state: merged
        collection_labels:
          - Support
          - Development
        group_by: month
        period_limit: 24

Example Project

What is the current bug behavior?

What is the expected correct behavior?

Relevant logs and/or screenshots

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info 
(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes

Edited by Magdalena Frankiewicz