I can't duplicate the behavior on my Jenkins controller that does not have Blue Ocean installed.  My declarative Pipeline correctly proceeded or aborted from the console log. Maybe the case is specific to having the Blue Ocean plugins installed?

My declarative Pipeline job looked like this:

pipeline {
    agent none
    stages {
        stage('Hello and Goodbye') {
            input {
                message 'Shall we proceed with the first greeting?'
                ok 'Yes, greet me first'
            }
            steps {
                echo 'Hello World'
                input message: 'Shall we proceed with the second greeting?', ok: 'Yes, please greet me again'
                echo 'Goodbye World'
            }
        }
    }
}

Does the failure happen when you do not have Blue Ocean installed?

naveenboni was there a reason that you listed this issue as "in progress"? Are you investigating it or trying to duplicate it?

Helo markewaite naveenboni , I am facing the same issue with Jenkins 2.426.1. Did you find any solution for this?

anvesh_gummala I didn't find a solution for this because I cannot duplicate the problem.

Can you describe the precise steps you take to duplicate the problem on a fresh installation of Jenkins?

I took the following steps and was unable to duplicate the problem:

1. Create a plugins.txt file that defines the exact plugins and versions I am using
2. Create a run-jenkins.sh that runs Jenkins 2.414.3 with the plugins defined in plugins.txt
3. Run the run-jenkins.sh script and complete the setup wizard by choosing to install no additional plugins
4. Define a declarative Pipeline job as noted in my earlier comment (two input steps)
5. Run the declarative Pipeline job from the "Build now" link (outside Blue Ocean) and confirm that each path through the input behaves as expected from the console log
6. Run the declarative Pipeline job from the Blue Ocean interface and confirm that the input prompts behave as expected from the Blue Ocean interface

Unless there is a response from you or from bremnertech, I will likely close this as "Cannot reproduce", since all my attempts to duplicate the issue have failed.

Helo markewaite , I am using Jenkins official image of docker to run the controller on Kubernetes. When I am using the latest LTS image jenkins/jenkins:2.426.1, I am facing this issue with interactive inputs. So I have downgraded the image to -2 i.e jenkins/jenkins:2.414.2-lts and the issue got resolved. Is there anything particular that got added on the last 2 LTS releases ? I have found this change but not sure whether it is related or not..

Replace browser confirm with modal dialogs in many places. Add API for alert, confirm, prompt, modal and form dialogs. (issue 71438) on 2.426.1

I will spin up another instance minus the blueocean plugin and report back

anvesh_gummala I performed the same steps with Jenkins 2.426.1 as I described earlier and i saw the same results as I had with Jenkins 2.414.3. I can't duplicate the issue.

The "Replace browser confirm with modal dialogs" did not affect the Pipeline input step. You'll need to provide instructions so that others can duplicate the issue.

I concur a fresh install of Jenkins 2.426.1 with / without blueocean allows pipeline-input-step plugin to feature. A local issue must be causing the problem which i will investigate offline.

Recommend closing ticket.

Closing as "Cannot reproduce" after two months with no response to the requests for additional information