### Summary When defining rules for inputs in gitlab-ci.yml, if we declare a if rule with more than 3 conditions, only the last 2 conditions are correctly evaluated in 'New Pipeline' UI ### Steps to reproduce - In .gitlab-ci.yml, Create an input 'main_selector' with 6 options - Create an input 'param_123' with rule to set value if main_selector value matches one of 3 first options (using 3 equals conditions with OR) - Create an input 'param_456' with rule to set value if main_selector value matches one of 3 last options (using 3 equals conditions with OR) - Create an input 'param_123456' with rule to set value if main_selector value matches one of the 6 options (using 6 equals conditions with OR) - In Pipelines page, create a 'New Pipeline' - Change value of 'main_selector' ### Example Project https://gitlab.com/PaysPlat/ciinputsrulestests/ ### What is the current *bug* behavior? - For 3 first values, we see only 'param_123' input - For the 4th value, we see only 'param_456' input - For 2 last values, we see 'param_456' & 'param_123456' inputs as exepected ### What is the expected *correct* behavior? - For 3 first values, we expect to see 'param_123' & 'param_123456' inputs - For 3 last values, we expect to see 'param_456' & 'param_123456' inputs ### Relevant logs and/or screenshots Correct behavior {width=900 height=223} Incorrect behavior {width=900 height=209} ### Output of checks <!-- If you are reporting a bug on GitLab.com, uncomment below --> This bug happens on GitLab.com <!-- and uncomment below if you have /label privileges --> /label ~"reproduced on GitLab.com" <!-- or follow up with an issue comment of `@gitlab-bot label ~"reproduced on GitLab.com"` if you do not -->