Currently, if a user tries to run a parametrised pipeline job or freestyle, it will likely not work as it will run the job without any mandatory parameters.

In Scope:

• Blue ocean should detect a parametrised job and the RUN button redirect to the run form on classic (at least until blue ocean supports setting of parameters).

Out of scope:

• A blue ocean form screen to capture these parameters.

Multibranch pipeline jobs are currently no parametrised so supporting trigger parameters is a lower priority for blue ocean, but given existing popularity of parametrised jobs, it seems wrong to just "break" them.