Skip to content

GitLab

Closed
Created by Administrator@rootOwner

Mentioning does not add user to list of participants

Created by: Delphinator

Summary

If you @mention somebody in either an issue or a comment to an issue, he/she does not get added to the list of participants and receives no notifications in return.

Steps to reproduce

  1. Install Gitlab
  2. create new group (let's call it devs)
  3. create additional user (let's call him joe)
  4. add joe to devs as Developer
  5. add new repository (let's call it awesome_project)
  6. create new issue in awesome_project and include @joe somewhere in the description
  7. comment this issue and include @joe somewhere

Expected behaviour

Joe is in the list of participants and receives a notification via email.

Observed behaviour

The list of participants only includes ourself and no notification is sent.

Relevant logs and/or screenshots

The logs show no attempt at sending a notification. The issue looks like this (I censored my name): Screenshot of the created issue

Output of checks

gitlabhost:/home/git/gitlab$ sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production
Checking Environment ...

Git configured for git user? ... yes
Has python2? ... yes
python2 is supported version? ... yes

Checking Environment ... Finished

Checking GitLab Shell ...

GitLab Shell version >= 1.7.0 ? ... OK (1.7.0)
Repo base directory exists? ... yes
Repo base directory is a symlink? ... no
Repo base owned by git:git? ... yes
Repo base access is drwxrws---? ... yes
post-receive hook up-to-date? ... yes
post-receive hooks in repos are links: ... 
[...]
devs / awesome_project ... repository is empty

Checking GitLab Shell ... Finished

Checking Sidekiq ...

Running? ... yes

Checking Sidekiq ... Finished

Checking GitLab ...

Database config exists? ... yes
Database is SQLite ... no
All migrations up? ... yes
GitLab config exists? ... yes
GitLab config outdated? ... no
Log directory writable? ... yes
Tmp directory writable? ... yes
Init script exists? ... yes
Init script up-to-date? ... no
  Try fixing it:
  Redownload the init script
  For more information see:
  doc/install/installation.md in section "Install Init Script"
  Please fix the error above and rerun the checks.
Projects have satellites? ... 
[...]
devs / awesome_project ... can't create, repository is empty
Redis version >= 2.0.0? ... yes
Your git bin path is "/usr/bin/git"
Git version >= 1.7.10 ? ... no
  Try fixing it:
  Update your git to a version >= 1.7.10 from 1.7.9
  Please fix the error above and rerun the checks.

Checking GitLab ... Finished

The init script and the old git version don't seem relevant at all.

sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production

System information
System:     Ubuntu 12.04
Current User:   git
Using RVM:  no
Ruby Version:   2.0.0p247
Gem Version:    2.0.3
Bundler Version:1.3.5
Rake Version:   10.1.0

GitLab information
Version:    6.0.1
Revision:   d422ee0
Directory:  /home/git/gitlab
DB Adapter: mysql2
URL:        https://CENSORED/gitlab
HTTP Clone URL: https://CENSORED/gitlab/some-project.git
SSH Clone URL:  git@CENSORED:some-project.git
Using LDAP: no
Using Omniauth: no

GitLab Shell
Version:    1.7.0
Repositories:   /home/git/repositories/
Hooks:      /home/git/gitlab-shell/hooks/
Git:        /usr/bin/git