Group level issue board upcoming milestone scope does not work

Summary

If you create a group level issue board with scope set to milestone and set that to "Upcoming" the open and close column will keep spinning forever.

Steps to reproduce

Pre requisites

  • A milestone with start after today and end date after start date (to make it "upcoming")
  • Open issues in this milestone
  • Closed issues in this 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 "Upcoming"
  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 open and closed column will keep "loading" forever.

What is the expected correct behavior?

Seeing the open and closed issues bound to the upcoming sprint in their rightful columns.

Relevant logs and/or screenshots

I see two errors logged to the browsers console. The stacktrace states "raven.js" which gives me a hint that you guys must be using sentry.io or something to track this error. I haven't found an issue on the issue tracker yet though. This is the error I see (removed the sensitive parts).

raven.js:1232 GET https://gitlab.com/-/boards/123456/lists/1234567/issues?id=1234567&milestone_title=%23upcoming&page=1 500 (Internal Server Error)
(anonymous) @ raven.js:1232
(anonymous) @ xhr.js:178
e.exports @ xhr.js:12
e.exports @ dispatchRequest.js:57
Promise.then (async)
c.request @ Axios.js:51
c.(anonymous function) @ Axios.js:61
(anonymous) @ bind.js:9
value @ board_service.js:63
value @ list.js:139
value @ list.js:25
e @ list.js:61
t @ list.js:16
addList @ boards_store.js:49
(anonymous) @ index.js:112
(anonymous) @ index.js:111
Promise.then (async)
mounted @ index.js:110
kt @ vue.esm.js:3034
(anonymous) @ vue.esm.js:2915
hn.$mount @ vue.esm.js:8655
hn.$mount @ vue.esm.js:11070
e._init @ vue.esm.js:4741
hn @ vue.esm.js:4828
t.a @ index.js:57
(anonymous) @ index.js:8
a @ raven.js:360

raven.js:1232 GET https://gitlab.com/-/boards/123456/lists/1234567/issues?id=1234567&milestone_title=%23upcoming&page=1 500 (Internal Server Error)
(anonymous) @ raven.js:1232
(anonymous) @ xhr.js:178
e.exports @ xhr.js:12
e.exports @ dispatchRequest.js:57
Promise.then (async)
c.request @ Axios.js:51
c.(anonymous function) @ Axios.js:61
(anonymous) @ bind.js:9
value @ board_service.js:63
value @ list.js:139
value @ list.js:25
e @ list.js:61
t @ list.js:16
addList @ boards_store.js:49
(anonymous) @ index.js:112
(anonymous) @ index.js:111
Promise.then (async)
mounted @ index.js:110
kt @ vue.esm.js:3034
(anonymous) @ vue.esm.js:2915
hn.$mount @ vue.esm.js:8655
hn.$mount @ vue.esm.js:11070
e._init @ vue.esm.js:4741
hn @ vue.esm.js:4828
t.a @ index.js:57
(anonymous) @ index.js:8
a @ raven.js:360

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)