<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label. For the Community Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ce/issues?label_name%5B%5D=bug For the Enterprise Edition issue tracker: - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab-ee/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ### Summary Discussion count gets updated by the changes I push to the merge request ### Steps to reproduce 1. Create a merge request from a branch to another. Let's say from develop to master 2. Go to the merge request page as you need to observe the count from Discussion tab 3. As you haven't added any comments on MR / on the code, the count will be 0 4. Now push a commit to develop branch and check the merge request page. Do not refresh it yet 5. Observe it for some time. You will see the Count in Discussion tab will get updated to 1 6. Refresh the page and the count will be 0 ### What is the current *bug* behavior? If I am not mistaken, count in Discussion tab from a merge request is for number of discussions on the Merge request only. And it shouldn't increase temporarily by changes I push to that repo. ### What is the expected *correct* behavior? Discussion count should not update by changes I push to the repo. ### Output of checks I am using GitLab Community Edition 10.6.4. Gitlab.com