dashboard>Milestones' menu shows WRONG DATA
Summary
When opening the Dashboard > Milestones menu, it shows 0 (ZERO) for all the tabs (Open, Closed, All) even if present.
In addition, when clicking one of the TABs, it always shows the list of OPEN MILESTONES for all of them, instead of the ones closed, or all of them accordingly.
Steps to reproduce
Create a few Group Milestones and close some of them. Under {Group} > Milestones they are showed correctly, but in Dashboard > Milestones they are not, as explained.
Example Project
Here, https://gitlab.com/milestones-bug, an example of the bug. I created a group "milestones-bug", then created 3 Milestones M1, M2, M3 and closed M1.
Under {Group}/Milestones it shows the milestones correctly:
However, under Dashboard > Milestones it shows the wrong milestones, with wrong counting:
What is the current bug behavior?
Under Dashboard > Milestones the count for the milestones is always ZERO, and each TAB shows the OPEN Milestones instead of the correct ones (CLOSED, ALL).
What is the expected correct behavior?
Under Dashboard > Milestones, show the correct count for the milestones, and for each TAB show the corresponding milestones (OPEN, CLOSED, ALL) instead of showing always the ALL view. (What you should see instead)
Relevant logs and/or screenshots
(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's very hard to read otherwise.)
Output of checks
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
)
Possible fixes
Probably it's related to the changes done for gitlab-ce#35748