Commit comment notifications going to wrong user
Forgive me if I miss anything or lack detail, this is my first time posting an issue.
Summary
When user A comments on user B's commit, the notification email gets sent to another user.
Steps to reproduce
Comment on a user's commit
Example Project
What is the current bug behavior?
When snyder comments on beachb's commit, beachb does not get a notification. The notification goes to another user.
What is the expected correct behavior?
beachb should receive a notification that snyder commented on their commit.
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: CentOS 6.9 Current User: git Using RVM: no Ruby Version: 2.3.3p222 Gem Version: 2.6.6 Bundler Version:1.13.7 Rake Version: 10.5.0 Redis Version: 3.2.5 Git Version: 2.11.1 Sidekiq Version:5.0.0
GitLab information Version: 9.2.2 Revision: cbde95c Directory: /opt/gitlab/embedded/service/gitlab-rails DB Adapter: postgresql URL: https://git.imsweb.com HTTP Clone URL: https://git.imsweb.com/some-group/some-project.git SSH Clone URL: git@git.imsweb.com:some-group/some-project.git Using LDAP: yes Using Omniauth: no
GitLab Shell Version: 5.0.4 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
Redis version >= 2.8.0? ... yes Ruby version >= 2.1.0 ? ... yes (2.3.3) Your git bin path is "/opt/gitlab/embedded/bin/git" Git version >= 2.7.3 ? ... yes (2.11.1) Active users: 153
Checking GitLab ... Finished
Possible fixes
Thought the issue was tied to https://gitlab.com/gitlab-org/gitlab-ce/issues/28755 however we've upgraded gitlab several times and are still having this issue.