Receiving notifications not in line with notification settings
Summary
Chat conversation at https://gitlab.slack.com/archives/questions/p1488300837009667, repeating here for clarity:
- I have my global notification level on GitLab.com set to "Participate".
- I have all the Groups and Projects that I am a part of on GitLab.com set to notify at the Global Notification level.
But then recently, an issue was re-assigned ( https://gitlab.com/gitlab-com/marketing/issues/858 ) and I was notified by email although I had never participated in the issue. This happened on
- https://gitlab.com/gitlab-com/marketing/issues/866
- https://gitlab.com/gitlab-com/marketing/issues/865
- https://gitlab.com/gitlab-com/marketing/issues/863
- https://gitlab.com/gitlab-com/marketing/issues/862
- https://gitlab.com/gitlab-com/marketing/issues/859
- https://gitlab.com/gitlab-com/marketing/issues/858
- https://gitlab.com/gitlab-com/marketing/issues/857
- https://gitlab.com/gitlab-com/marketing/issues/856
- https://gitlab.com/gitlab-com/marketing/issues/855
- https://gitlab.com/gitlab-com/marketing/issues/854
- https://gitlab.com/gitlab-com/marketing/issues/853
- https://gitlab.com/gitlab-com/marketing/issues/852
- https://gitlab.com/gitlab-com/marketing/issues/849
There may be a different or related bug here; @mitchellwright can comment.. on many of these issues it appears that Mitchell assigned to himself, then quickly unassigned again. I only received email notification of the assignation, not of the unassigning.
Steps to reproduce
No clue.
What is the current bug behavior?
See above.
What is the expected correct behavior?
I should only receive emails for issues in which I participate(d).
Relevant logs and/or screenshots
n/a
Output of checks
This bug happens on GitLab.com.
Results of 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
(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)