With multiple issue boards, removal of list labels when closing an issue is overly broad
Summary
For a scrum-style setup using labels for sprints, the sprint label is removed when an issue is closed via a board
Steps to reproduce
Create some labels: Sprint 1, Sprint 2, In Progress, QA
Create two boards:
- Current Sprint: filter on label = Sprint 1, add lists: In Progress, QA
- Sprint Planning: no filtering, add lists: Sprint 1, Sprint 2
Create an issue on the Current Sprint board. It should have the Sprint 1 label attached. Drag it to In Progress column; now it also has the In Progress label. Drag it to QA; In Progress has been removed, QA has been added. Drag it to Done; QA has been removed (desirable), Sprint 1 has also been removed (possibly only after reloading the board). The removal of the Sprint 1 label is undesired behavior.
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?
When closing an issue using a board, all list labels are removed, where list labels are the labels used on any board.
What is the expected correct behavior?
When closing an issue using a board, only the labels used as lists on the current board should be removed.
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
(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
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)