Commit message with fast-forward merge method and squash is "random" and unable to edit

Summary

If a project is set to use Fast-Forward merge method; and the squash commit option is used the resulting commit message is basically random with no option to edit it before merging.

Steps to reproduce

1. Set Merge method of the project to "Fast-forward merge"
2. Create a new Merge request with multiple commits
3. Select "squash commits" when merging the merge request

What is the current bug behavior?

I believe the commit message ends up being either: (based on https://docs.gitlab.com/ee/user/project/merge_requests/squash_and_merge.html)

• Taken from the first multi-line commit message in the merge.
• The merge request’s title if no multi-line commit message is found.

There is no option present to edit the message before merging.

What is the expected correct behavior?

Previously the commit message was the MR description if multiple commits were present on the MR; if only a single commit it was the commit's message.

The ability to edit the message would be the expected behavior.

Relevant logs and/or screenshots

Unable due to being on a closed network

Results of GitLab environment info

Unable due to being on a closed network

Results of GitLab application Check

Unable due to being on a closed network

Running 11.8.1-ee

Possible fixes

None right now