The Pipeline as code can promote for parameter value input, but it holds the executor. Our use case is to provide approval note from one stage to another, which may happen several days later.
I have implemented a workaround in our case for now.
Let the Manual Approving Job check a file parameter to decide to move forward or not.
Then created another job to accept values for the parameter and save it to a file.
In the Build pipeline, a string parameter is used to create a link to the parameter entering job, and it is displayed in the reversion box.
the links is like
<a onclick="buildPipeline.fillDialog('job/ParameterEntering/build?delay=0sec', 'Enter Parameters')"> Enter Parameters</a>
This will popup the job in a lightbox within the build pipeline.
It is complicated and just a workaround. We really hope if this issue can get fixed soon.