Skip to content

Group level issue board scoped to running milestone show to many closed issues

Summary

Group level issue board with scope set to Milestone "Started" shows all closed issues in the closed column.

Steps to reproduce

Pre requisites

  • A milestone with start before today and end date after today (to make it "current")
  • Open issues in this milestone
  • Closed issues in this milestone
  • Closed issues not in this milestone but some other (expired) milestone
  • Closed issues not bound to any milestone

Steps

  1. Go to a group page (i.e. https://gitlab.com/somegroup)
  2. Go to Issues -> Boards
  3. Create a new board via "Switch Board" dropdown -> "Create New Board"
  4. Give it some awesome name 🚀
  5. Click on "Expand" next to Board Scope
  6. Click on edit next to milestone
  7. Pick "Started"
  8. Click "Create board" on the bottom

Example Project

We are running Gitlab silver via gitlab.com, all our projects are currently private hence I cannot share them here.

What is the current bug behavior?

The closed column to the right will show all closed issues, also the issues that are not related to the "started" milestone.

What is the expected correct behavior?

The board is supposed to be about the current running milestone(s). So it should only show closed issues that are related to that milestone(s). I get that it potentially can show more active milestones because of the "running" factor, but now it just shows all the closed issues. That does not make sense, it is cluttering and confusing.

Relevant logs and/or screenshots

Not relevant.

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Not relevant.

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

Not relevant.

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)

Edited by Jogchum Koerts