In the BlueOcean UI for a build, the "Rerun" button (circular arrow) on the top bar, will trigger the build again. But the new build is triggered as a "Replay" and not a "Rebuild", even though the user gets no chance to edit the Jenkinsfile/groovy scripts.

In my organization, we have logic to e.g. not allow releases to be built from "Replay" runs (as we don't know what groovy code was actually used). This makes the "Rerun" button unusable for retriggering release or release candidate builds.

Suggested improvement:
Let the Rerun button trigger a rebuild, i.e. be equivalent to using "Rebuild" in the classic UI.

(Or, possibly, have different buttons in BlueOcean for both Replay and Rebuild, and give the user the possibility to modify scripts in the Replays.)