Pipelines must succeed option behavior has changed

Summary

Pipelines must succeed option behavior has changed

Steps to reproduce

With Gitlab 12.0.3-ee.0 if the option "Pipelines must succeed" was set and no Jenkins pipeline (I guess also true with Gitlab pipeline) was defined, then it was possible to merge a merge request

With Gitlab 12.2.4-ee.0 with the same conditions it is no more possible to merge a merge request. Moreover nothing into the UI explains clearly why it is not possible to merge

Cf "Relevant logs and/or screenshots" section

Example Project

What is the current bug behavior?

See "Steps to reproduce" section

What is the expected correct behavior?

Either go back to the behavior of version 12.0.3-ee.0, or improve UI display to explain that it is not possible to merge because no pipeline is defined

Note that the only ticket related to "Pipelines must succeed" that I have found is https://gitlab.com/gitlab-org/gitlab-ce/issues/64461 But the problem is slightly different and not already delivered

Relevant logs and/or screenshots

UI when the option is set

GitlabWithOption

UI when the option is not set

GitlabWithoutOption

Output of checks

(If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com)

Results of GitLab environment info

Results of GitLab application Check

Possible fixes

Assignee Loading
Time tracking Loading