Default.md merge request template does not show up in merge requests

Summary

Despite having a .gitlab/merge_request_templates/default.md file in our repository, it is not used when I open a new MR. There's also no template selection dropdown.

Steps to reproduce

  • Create project as part of a group,
  • Add .gitlab/merge_request_templates/default.md file to default branch (in our case this branch is named development),
  • Create a branch with one new commit and open a new merge request against the development branch (mr branch is based on the latest version of the default branch so it also has the merge request template file),
  • Observe that the description is still empty and there is no template selection dropdown.

What is the current bug behavior?

Description is empty and no template dropdown is available.

What is the expected correct behavior?

Description contains the contents of the default.md file.

Maybe there should also be a dropdown for selecting a template, but I'm not sure about that when you have only one template and it's named default.md.

Relevant logs and/or screenshots

The documentation for this feature mentions the following prerequisite:

Ensure issues or merge requests are set to either Everyone with access or Only Project Members.

For me it first looked like this:

image

The selection is empty and does not contain the text 'Only Project Members'. The dropdown is disabled so I can't change the value.

After toggling the switches to the left off and on it shows 'Only Project Members' in the corresponding dropdown. After doing that and hitting save, it now always shows 'Only Project Members' in the dropdowns:

image

Not sure if that has anything to do with our issue or if it's just a distraction.

Output of checks

Results of GitLab environment info

Expand for output related to GitLab environment info
System information
System:         Debian 10
Proxy:          no
Current User:   git
Using RVM:      no
Ruby Version:   2.7.5p203
Gem Version:    3.1.6
Bundler Version:2.3.15
Rake Version:   13.0.6
Redis Version:  6.2.7
Sidekiq Version:6.4.0
Go Version:     unknown

GitLab information
Version:        15.3.3-ee
Revision:       1615d086ad8
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     PostgreSQL
DB Version:     12.10
URL:            https://gitlab.ek.co
HTTP Clone URL: https://gitlab.ek.co/some-group/some-project.git
SSH Clone URL:  git@gitlab.ek.co:some-group/some-project.git
Elasticsearch:  no
Geo:            no
Using LDAP:     no
Using Omniauth: yes
Omniauth Providers: bitbucket

GitLab Shell
Version:        14.10.0
Repository storage paths:
- alternative:  /data/git-data/repositories
GitLab Shell path:              /opt/gitlab/embedded/service/gitlab-shell

Results of GitLab application Check

Expand for output related to the GitLab application check
Checking GitLab subtasks ...

Checking GitLab Shell ...

GitLab Shell: ... GitLab Shell version >= 14.10.0 ? ... OK (14.10.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: ... alternative ... OK

Checking Gitaly ... Finished

Checking Sidekiq ...

Sidekiq: ... Running? ... yes Number of Sidekiq processes (cluster/worker) ... 1/1

Checking Sidekiq ... Finished

Checking Incoming Email ...

Incoming Email: ... Reply by email is disabled in config/gitlab.yml

Checking Incoming Email ... Finished

Checking LDAP ...

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

Checking LDAP ... Finished

Checking GitLab App ...

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 Systemd unit files or init script exist? ... skipped (omnibus-gitlab has neither init script nor systemd units) Systemd unit files or init script up-to-date? ... skipped (omnibus-gitlab has neither init script nor systemd units) Projects have namespace: ... 2/1 ... yes 5/5 ... yes 1/6 ... yes 5/7 ... yes 6/8 ... yes 5/11 ... yes 6/13 ... yes 5/14 ... yes 12/15 ... yes 5/16 ... yes 5/17 ... yes 5/18 ... yes 5/19 ... yes 5/20 ... yes 14/21 ... yes 14/22 ... yes 5/23 ... yes 5/24 ... yes 14/25 ... yes 14/26 ... yes 5/27 ... yes 14/28 ... yes 31/29 ... yes 5/30 ... yes 5/31 ... yes 5/33 ... yes 5/34 ... yes 31/36 ... yes 5/37 ... yes 8/38 ... yes 35/39 ... yes 35/40 ... yes 35/42 ... yes 35/43 ... yes 5/44 ... yes 5/45 ... yes 35/46 ... yes 5/47 ... yes 129/48 ... yes 129/49 ... yes 40/50 ... yes 129/51 ... yes 129/52 ... yes 43/54 ... yes 40/55 ... yes 38/57 ... yes 8/58 ... yes 35/59 ... yes 35/60 ... yes 129/62 ... yes 129/63 ... yes 5/64 ... yes 38/65 ... yes 35/66 ... yes 5/67 ... yes 119/69 ... yes 121/70 ... yes 35/71 ... yes 34/72 ... yes 129/73 ... yes 40/74 ... yes 35/75 ... yes 129/76 ... yes 43/77 ... yes 40/78 ... yes 5/79 ... yes 51/80 ... yes 35/81 ... yes 31/82 ... yes 35/83 ... yes 5/84 ... yes 5/85 ... yes 35/86 ... yes 35/87 ... yes 35/89 ... yes Redis version >= 6.0.0? ... yes Ruby version >= 2.7.2 ? ... yes (2.7.5) Git user has default SSH configuration? ... yes Active users: ... 39 Is authorized keys file accessible? ... yes GitLab configured to store new projects in hashed storage? ... yes All projects are in hashed storage? ... yes Elasticsearch version 7.x-8.x or OpenSearch version 1.x ... skipped (Advanced Search is disabled)

Checking GitLab App ... Finished

Checking GitLab subtasks ... Finished

Edited Sep 09, 2022 by Dexter Döpping
Assignee Loading
Time tracking Loading