Label and Issue Status Relevance

Summary

When closing the Issue on GitLab.com, I tried the following two methods. With these two methods, the Label state when the Issue is closed is different. <\p>

GitLab.comでIssueをcloseする際、以下の2つの方法を試しました。
この2通りの方法で、Issueがcloseされた際のLabelの状態が異なります。

Steps to reproduce

Case 1:
Click "close issue" on the "Group> Subgroup> Project> #Issue number" screen.
-> After clicking "close issue", the issue is closed with a label attached.
(See Inquiry_Issue01.PNG and Inquiry_Issue02.PNG)
Inquiry_Issue01
Inquiry_Issue02

Case 2:
Close the issue by drag and drop on the "Group> Subgroup> Issue Boards" screen.
-> When an issue with a label is dragged and dropped to close, the issue is closed with the label deleted.
(See Inquiry_Issue03.PNG and Inquiry_Issue04.PNG)
Inquiry_Issue03
Inquiry_Issue04

Why these situation is different ? If it was a specification, is it possible to delete a specific label from the issue and close it when clicking “close issue” in Case1?

1.「Group > Subgroup > Project > #Issue番号」画面で「close issue」をクリックする
->「close issue」をクリック後、IssueはLabelが付与された状態でcloseされる。
（「Inquiry_Issue01.PNG」および「Inquiry_Issue02.PNG」参照）
2.「Group > Subgroup > Issue Boards」画面で、ドラッグアンドドロップによってIssueをcloseする
-> Labelが付与されたIssueをcloseにドラッグアンドドロップすると、IssueはLabelが削除された状態でcloseされる。
（「Inquiry_Issue03.PNG」および「Inquiry_Issue04.PNG」参照）

Example Project

(If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report)

We tested only the following Private project. This Enviroment is Gitrab.com SaaS. https://gitlab.com/kc_develop/

Your request (140943) has been updated. To add additional comments, reply to this email.
Cynthia Ng (GitLab, Inc.)
Dec 9, 14:56 EST
Hi,
Thanks for contacting GitLab Support.
Would you be willing to move the issue to our GitLab project issue tracker? That way the issue is public and our development team will be able to see it as well.
Regards,
Cynthia Ng
Senior Support Agent, GitLab Inc.

(If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version)

What is the current bug behavior?

(What actually happens)

What is the expected correct behavior?

(What you should see instead)

Relevant logs and/or screenshots

(Paste any relevant logs - please use code blocks (```) to format console output, logs, and code as it's tough 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)

Edited by Kozo Tao