Moving an issue-card from a list to backlog removes milestone and all labels
Summary
- when an issue is moved back to backlog, all labels and the milestone is removed, which is not what is intended
Steps to reproduce
- Having issue boards with at least 3 columns: "backlog (builtin)", "doing" and "closed (builtin)"
- having the board setup to show only "started milestones"
- having an issue in "doing" with multiple other labels and a started milestone attached
- move the issue to backlog.
- all labels and milestone is removed from issue
What is the current bug behavior?
- all labels and milestone is removed from issue
What is the expected correct behavior?
- only the label from the list, it was in should be removed.htop
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 18.04 Proxy: no Current User: git Using RVM: no Ruby Version: 2.4.4p296 Gem Version: 2.7.6 Bundler Version:1.16.2 Rake Version: 12.3.1 Redis Version: 3.2.11 Git Version: 2.18.1 Sidekiq Version:5.1.3 Go Version: unknown
GitLab information Version: 11.3.4-ee Revision: 14d3a1dcd51 Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql DB Version: 9.6.8 URL: https://git.***** HTTP Clone URL: https://git./some-group/some-project.git SSH Clone URL: git@git.:some-group/some-project.git Elasticsearch: no Geo: no Using LDAP: yes Using Omniauth: no
GitLab Shell Version: 8.3.3 Repository storage paths:
- default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git
Results of GitLab application Check
Expand for output related to the GitLab application check
gitlab-rake gitlab:check SANITIZE=true Checking GitLab Shell ...GitLab Shell version >= 8.3.3 ? ... OK (8.3.3) 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: ... 20/8 ... ok 6/9 ... ok 6/10 ... ok 6/11 ... ok 6/12 ... ok 6/13 ... ok 6/14 ... ok 6/15 ... ok 6/16 ... ok 6/17 ... ok 6/20 ... ok 6/21 ... ok 20/22 ... ok 20/24 ... ok 20/25 ... ok 20/26 ... ok 9/27 ... ok 9/28 ... ok 11/29 ... repository is empty 20/30 ... ok 20/31 ... ok 6/32 ... repository is empty 20/33 ... ok 6/34 ... repository is empty Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Check GitLab API access: OK Redis available via internal API: OK
Access to /var/opt/gitlab/.ssh/authorized_keys: 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 ...
IMAP server credentials are correct? ... yes Init.d configured correctly? ... skipped MailRoom running? ... skipped
Checking Reply by email ... Finished
Checking LDAP ...
Server: ldapmain LDAP authentication... Success LDAP users with access to your GitLab server (only showing the first 100 results) [...]
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? ... no Try fixing it: sudo chown -R git /var/opt/gitlab/gitlab-rails/uploads sudo find /var/opt/gitlab/gitlab-rails/uploads -type f -exec chmod 0644 {} ; sudo find /var/opt/gitlab/gitlab-rails/uploads -type d -not -path /var/opt/gitlab/gitlab-rails/uploads -exec chmod 0700 {} ; For more information see: doc/install/installation.md in section "GitLab" Please fix the error above and rerun the checks. Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 20/8 ... yes 6/9 ... yes 6/10 ... yes 6/11 ... yes 6/12 ... yes 6/13 ... yes 6/14 ... yes 6/15 ... yes 6/16 ... yes 6/17 ... yes 6/20 ... yes 6/21 ... yes 20/22 ... yes 20/24 ... yes 20/25 ... yes 20/26 ... yes 9/27 ... yes 9/28 ... yes 11/29 ... yes 20/30 ... yes 20/31 ... yes 6/32 ... yes 20/33 ... yes 6/34 ... yes Redis version >= 2.8.0? ... yes Ruby version >= 2.3.5 ? ... yes (2.4.4) Git version >= 2.9.5 ? ... yes (2.18.1) Git user has default SSH configuration? ... yes Active users: ... 9 Elasticsearch version 5.1 - 5.5? ... skipped (elasticsearch is disabled)
Checking GitLab ... Finished