Boards do not filter by Upcoming milestone
Summary
The "Upcoming" milestone choice in Boards does not actually filter based upon "Upcoming" milestones.
Steps to reproduce
- Set milestones so that one is during the current time and a second is during a future time frame
- Ensure there are issues marked with the first milestone and other issues marked with the second milestone
- Create a new Board
- Set the milestone for the new Board to "Upcoming"
- Add list as-needed to see the issues from step 2
- Note that issues from the current time milestone show in addition to issues from the future time frame second milestone
Example Project
(If possible, please create an example project here on GitLab.com that exhibits the problematic behaviour, 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 has been fixed in a more recent version)
What is the current bug behavior?
The Board is not filtered down to only "Upcoming" milestone issues
What is the expected correct behavior?
The Board should be filtered down to only "Upcoming" milestone issues
Relevant logs and/or screenshots
Note in this screenshot that GitLab indicates that 4.0.29
is not "Upcoming" and that 4.1.5
is "Upcoming".
This screenshot shows that there is an issue in 4.0.29
and that a board can show that
This screenshot shows that there is an issue in 4.1.5
and that a board can show that
This screenshot shows that the "Upcoming" milestone's issues are not being shown.
Output of checks
Results of GitLab environment info
[root@gitlab gitlab]# sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production
System information
System:
Proxy: no
Current User: git
Using RVM: no
Ruby Version: 2.3.3p222
Gem Version:
Bundler Version:1.14.5
Rake Version: 10.5.0
Redis Version: 3.0.3
Git Version: 2.9.3
Sidekiq Version:5.0.0
Go Version: go1.8.3 linux/amd64
GitLab information
Version: 9.3.6-ee
Revision: 7046350
Directory: /home/git/gitlab
DB Adapter: postgresql
DB Version: 9.4.9
URL: http://gitlab.medstrat.com
HTTP Clone URL: http://gitlab.medstrat.com/some-group/some-project.git
SSH Clone URL: git@gitlab.medstrat.com:some-group/some-project.git
Elasticsearch: no
Geo: no
Using LDAP: no
Using Omniauth: no
GitLab Shell
Version: 5.1.1
Repository storage paths:
- default: /home/git/repositories
Hooks: /home/git/gitlab-shell/hooks
Git: /usr/bin/git
[root@gitlab gitlab]#
Results of GitLab application Check
[root@gitlab gitlab]# sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true
Checking GitLab Shell ...
GitLab Shell version >= 5.1.1 ? ... OK (5.1.1)
Repo base directory exists?
default... yes
Repo storage directories are symlinks?
default... no
Repo paths owned by git:root, or git:git?
default... yes
Repo paths access is drwxrws---?
default... yes
hooks directories in repos are links: ...
71/74 ... ok
71/75 ... ok
71/77 ... ok
71/78 ... ok
71/80 ... ok
71/81 ... ok
71/82 ... ok
71/83 ... ok
71/84 ... ok
71/85 ... ok
71/86 ... ok
71/87 ... ok
71/93 ... ok
71/96 ... ok
71/97 ... ok
71/99 ... ok
71/101 ... ok
71/102 ... ok
65/106 ... ok
71/108 ... ok
65/111 ... ok
65/113 ... ok
71/115 ... ok
65/116 ... ok
65/118 ... ok
65/120 ... ok
65/123 ... ok
9/124 ... ok
52/125 ... ok
69/128 ... ok
69/129 ... ok
65/132 ... ok
32/133 ... ok
69/135 ... ok
71/137 ... ok
32/138 ... ok
71/139 ... ok
71/140 ... ok
65/141 ... ok
61/142 ... repository is empty
63/175 ... ok
52/176 ... repository is empty
Running /home/git/gitlab-shell/bin/check
Check GitLab API access: OK
Access to /home/git/.ssh/authorized_keys: OK
Send ping to redis server: OK
gitlab-shell self-check successful
Checking GitLab Shell ... Finished
Checking Sidekiq ...
Running? ... yes
Number of Sidekiq processes ... 1
Checking Sidekiq ... Finished
Checking Reply by email ...
Reply by email is disabled in config/gitlab.yml
Checking Reply by email ... Finished
Checking LDAP ...
LDAP is disabled in config/gitlab.yml
Checking LDAP ... Finished
Checking GitLab ...
Git configured correctly? ... yes
Database config exists? ... yes
All migrations up? ... yes
Database contains orphaned GroupMembers? ... no
GitLab config exists? ... yes
GitLab config up to date? ... yes
Log directory writable? ... yes
Tmp directory writable? ... yes
Uploads directory exists? ... yes
Uploads directory has correct permissions? ... yes
Uploads directory tmp has correct permissions? ... yes
Init script exists? ... yes
Init script up-to-date? ... yes
Projects have namespace: ...
71/74 ... yes
71/75 ... yes
71/77 ... yes
71/78 ... yes
71/80 ... yes
71/81 ... yes
71/82 ... yes
71/83 ... yes
71/84 ... yes
71/85 ... yes
71/86 ... yes
71/87 ... yes
71/93 ... yes
71/96 ... yes
71/97 ... yes
71/99 ... yes
71/101 ... yes
71/102 ... yes
65/106 ... yes
71/108 ... yes
65/111 ... yes
65/113 ... yes
71/115 ... yes
65/116 ... yes
65/118 ... yes
65/120 ... yes
65/123 ... yes
9/124 ... yes
52/125 ... yes
69/128 ... yes
69/129 ... yes
65/132 ... yes
32/133 ... yes
69/135 ... yes
71/137 ... yes
32/138 ... yes
71/139 ... yes
71/140 ... yes
65/141 ... yes
61/142 ... yes
63/175 ... yes
52/176 ... yes
Redis version >= 2.8.0? ... yes
Ruby version >= 2.3.3 ? ... yes (2.3.3)
Git version >= 2.7.3 ? ... yes (2.9.3)
Active users: ... 40
Elasticsearch version 5.1 - 5.3? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished
[root@gitlab gitlab]#
Possible fixes
N/A