Total Contributions column within the Contribution Analytics does not always equal the sum of the other columns
Summary
The Contribution Analytics column "Total Contributions" does not always equal the sum of the other columns. Please see below for 2 examples. Their sum is actually 57 and 17 respectively.
@ahegyi noted this may be a bug. The discrepancy is the number of MRs the user closed (without merge). We do not have a closed MRs column.
Steps to reproduce
Have a user close MRs without merging to see if it affects the "Total Contributions" column.
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)
(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)
What is the current bug behavior?
The Total Contributions column is showing more than the sum of the other columns. This may be occurring because number of MRs the user closed without merging is not showing as a column.
What is the expected correct behavior?
Total Contributions column accurately reflects the sum from all the other columns.
Relevant logs and/or screenshots
See above screenshot.
Output of checks
(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)
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
(If you can, link to the line of code that might be responsible for the problem)