Skip to content

"project name suffix" option is not visible in "Service Desk" settings (Need to improve documentation)

Summary

"project name suffix" option is not visible in "Service Desk" settings. I have already enabled "Feature.enable(:service_desk_custom_address)" although it should be enabled by default.

Steps to reproduce

  1. Enable incoming email and enable service desk for a project.
  2. Goto your Project's settings -> General -> Service Desk -> Expand it and "project name suffix" option should be there but it is not.
  3. As per "https://docs.gitlab.com/ee/user/project/service_desk.html" it should be available in 'Core' version and I am on CE version (13.7.0), so this should be available.

Example Project

This issue is not reproducing in the gitlab.com sample project.

What is the current bug behavior?

"project name suffix" option is not visible in "Service Desk" settings

What is the expected correct behavior?

"project name suffix" option should be visible in "Service Desk" settings

Relevant logs and/or screenshots

gitlab_missing

Output of checks

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`)

System information
System:		
Current User:	git
Using RVM:	no
Ruby Version:	2.7.2p137
Gem Version:	3.1.4
Bundler Version:2.1.4
Rake Version:	13.0.1
Redis Version:	5.0.9
Git Version:	2.29.0
Sidekiq Version:5.2.9
Go Version:	unknown

GitLab information
Version:	13.7.0
Revision:	91da1dcc7a1
Directory:	/opt/gitlab/embedded/service/gitlab-rails
DB Adapter:	PostgreSQL
DB Version:	11.9
URL:		http://myurl
HTTP Clone URL:	http://myurl/some-group/some-project.git
SSH Clone URL:	git@myurl:some-group/some-project.git
Using LDAP:	no
Using Omniauth:	yes
Omniauth Providers: 

GitLab Shell
Version:	13.14.0
Repository storage paths:
- default: 	/var/opt/gitlab/git-data/repositories
GitLab Shell path:		/opt/gitlab/embedded/service/gitlab-shell
Git:		/opt/gitlab/embedded/bin/git



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)

Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 13.14.0 ? ... OK (13.14.0) Running /opt/gitlab/embedded/service/gitlab-shell/bin/check Internal API available: OK Redis available via internal API: OK gitlab-shell self-check successful

Checking GitLab Shell ... Finished

Checking Gitaly ...

Gitaly: ... default ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes ... 1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Checking Reply by email ...

IMAP server credentials are correct? ... Checking myticket@gmail.com yes Init.d configured correctly? ... skipped MailRoom running? ... skipped

Checking Reply by email ... Finished

Checking Incoming Email ... Finished

Checking LDAP ...

LDAP: ... LDAP is disabled in config/gitlab.yml

Checking LDAP ... Finished

Checking GitLab App ...

Git configured correctly? ... yes Database config exists? ... yes All migrations up? ... yes Database contains orphaned GroupMembers? ... no GitLab config exists? ... yes GitLab config up to date? ... yes Log directory writable? ... yes Tmp directory writable? ... yes Uploads directory exists? ... yes Uploads directory has correct permissions? ... yes Uploads directory tmp has correct permissions? ... yes Init script exists? ... skipped (omnibus-gitlab has no init script) Init script up-to-date? ... skipped (omnibus-gitlab has no init script) Projects have namespace: ... 5/1 ... yes 5/2 ... yes 5/4 ... yes 5/5 ... yes 5/6 ... yes 5/7 ... yes 5/8 ... yes 5/9 ... yes 5/10 ... yes 5/11 ... yes 5/12 ... yes 5/13 ... yes 5/14 ... yes 47/15 ... yes 47/16 ... yes 47/17 ... yes 47/18 ... yes 5/19 ... yes 14/20 ... yes 5/21 ... yes 5/22 ... yes 5/24 ... yes 9/25 ... yes 5/27 ... yes 41/28 ... yes 9/29 ... yes 9/30 ... yes 41/33 ... yes 3/38 ... yes 41/41 ... yes 5/43 ... yes 8/44 ... yes 85/46 ... yes 86/48 ... yes 86/49 ... yes 86/50 ... yes 85/51 ... yes 85/52 ... yes 91/53 ... yes 91/54 ... yes 15/55 ... yes 65/56 ... yes 41/57 ... yes 41/59 ... yes 41/60 ... yes 41/63 ... yes 4/64 ... yes 86/65 ... yes 41/66 ... yes 9/67 ... yes 5/68 ... yes 94/69 ... yes 38/70 ... yes 38/71 ... yes 41/72 ... yes 104/73 ... yes 41/75 ... yes Redis version >= 4.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.2) Git version >= 2.29.0 ? ... yes (2.29.0) Git user has default SSH configuration? ... yes Active users: ... 71 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Possible fixes

See #295640 (comment 571577737)

Improve docs at https://docs.gitlab.com/ee/user/project/service_desk.html#using-custom-email-address to mention custom project suffix in the title, along with some tweaks to the text to better explain how to use it.

Edited by John Hope