Issue board has several updating bugs
The issue board seems to have a few performance issues:
- In lists with many issues, not all issues are shown when scrolling through the issues and looking at them one by one. After removing a few issues and refreshing the page, new issues appear
- Updates to the order of the list are not retained after refreshing the page
- Updates to issues on the board (e.g. changing assignee or labels) are not retained after refreshing the page
- Updates to the order of issues in one list are not retained after refreshing the page
Steps to reproduce
Create an issue board on the group level of several projects with many issues and several lists so that scrolling down the list is required to see all issues in it. Scroll down the whole list and remove the list label from a few issues. Refresh the page and scroll through the same list, additional issues that weren't visible before will appear. Try changing the order of the lists and refresh the page, the old order (or some other order) will be shown afterwards. Try changing the labels/assignees of a few issues, again the changes will be lost after refreshing the page
(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?
Changes made to the board are lost after refreshing the page. Also, not all issues in one list are displayed and additional issues appear after refreshing the board.
What is the expected correct behavior?
All issues that belong to a certain list should be displayed at all times, changes made to the order of lists or issues on the board should be retained.
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
(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
System information System: Ubuntu 16.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.5.3p105 Gem Version: 2.7.6 Bundler Version:1.16.6 Rake Version: 12.3.2 Redis Version: 3.2.12 Git Version: 2.18.1 Sidekiq Version:5.2.5 Go Version: go1.6.2 linux/amd64
GitLab information Version: 11.9.0-ee Revision: 2f3536b Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.11 URL: https://gitlab.athion.de HTTP Clone URL: https://gitlab.athion.de/some-group/some-project.git SSH Clone URL: firstname.lastname@example.org:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: no Using Omniauth: yes Omniauth Providers: gitlab
GitLab Shell Version: 8.7.1 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories GitLab Shell path: /opt/gitlab/embedded/service/gitlab-shell Git: /opt/gitlab/embedded/bin/git
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)
(If you can, link to the line of code that might be responsible for the problem)