This - WIP: is not the same as this WIP when working with merge requests.

Summary

When creating a MR with WIP in the title the MR is placed into the Work In Progress mode.

Steps to reproduce

  1. Create a new MR with the term WIP at any location in the title with the exception of the last.
  2. Make a commit.
  3. Attempt to merge.

What is the current bug behavior?

When creating an MR that has WIP in the title, and not WIP: at the begining of the title Gitlab treats the MR as a work in progress. Essentially the MR Running WIP GP is not the same as WIP: Running WIP GP despite WIP being an acronym for Work In Progress in both instances.

What is the expected correct behavior?

Creating a MR with the Title prefixed with WIP: should be handled as Work In Progress, while creating a MR title containing WIP should be handled as an Open MR.

Relevant logs and/or screenshots

image

System information
System:         Ubuntu 16.04
Current User:   git
Using RVM:      no
Ruby Version:   2.4.5p335
Gem Version:    2.7.6
Bundler Version:1.16.2
Rake Version:   12.3.1
Redis Version:  3.2.12
Git Version:    2.18.1
Sidekiq Version:5.2.1
Go Version:     go1.6.2 linux/amd64

GitLab information
Version:        11.4.6
Revision:       10ecd45
Directory:      /opt/gitlab/embedded/service/gitlab-rails
DB Adapter:     postgresql
URL:            http://dev2/gitlab
HTTP Clone URL: http://dev2/gitlab/some-group/some-project.git
SSH Clone URL:  git@dev2:some-group/some-project.git
Using LDAP:     yes
Using Omniauth: yes
Omniauth Providers:


GitLab Shell
Version:        8.3.3
Repository storage paths:
  • default: /var/opt/gitlab/git-data/repositories Hooks: /opt/gitlab/embedded/service/gitlab-shell/hooks Git: /opt/gitlab/embedded/bin/git