I am not 100% clear on the validation yet - I think some more research needed to know what is current behavior/possible/ideal - but this sounds like something to aim for.

michaelneale brody I can't think of a good reason why you wouldn't want to validate here (I suspect lack of validation in classic was an oversight rather than by design)

Zeplin https://zpl.io/ZwQgQM

Mockup

I put some details on how to get at the real data in the description.

The following is a pipeline that excercises all types of input we want to support at the moment - you can run this, and log at the console to get to a form that you can fill in to try it if you like:

node {
    stage("parallelStage"){
            echo "running"
            def branchInput = input id: 'CustomIdHere', message: 'this is a message to user', ok: 'Go ahead', parameters: [
                booleanParam(defaultValue: false, description: 'yes or no', name: 'thisIsBool'), 
                choice(choices: 'c1\nc2', description: 'this is choice description', name: 'This is choice'), 
                text(defaultValue: 'default', description: 'Long text goes here', name: 'This is a multi line string'), 
                string(defaultValue: 'yeah', description: 'string parameter desc', name: 'this is a string parmeter'), 
                password(defaultValue: 'secret', description: 'password param desc', name: 'password param')
            ]
            echo "BRANCH NAME: ${branchInput}"
    }
}

Note that it shows a choice as a drop down cc brody jamesdumay - (we wouldn't have both radio and drop down - which should it be - as there is only one "choice" type?)

What this looks like in Jenkins today on the console screen:

brody I don't think we should have an 'abort' button. The affirmative should be "Continue" instead of "Submit"?

jamesdumay brody currently the user can enter the text for the proceed button (but not the cancel). It is really a "continue or not" function - however it is worded (not continuing does not mean failure necessarily)

jamesdumay michaelneale I'm happy for you guys to make the call. Abort does sound a little extreme but what happens if you choose not to Input? "Skip"? or just nothing?

brody I'm not sure why the original feature in pipeline stage view had a way to "abort" the run but I know people have been frustrated thinking this was a "cancel" (if you abort, then the run is killed for ever).

You can't skip an input - its required before proceeding.

yes you have to have a way to cancel/abort/whatever we call. It halts the run from proceeding. "Abort" is probably fine wording. I think we discussed once that "cancel" was bad wording, as it may imply they are just cancelling the form, not the run. "Continue" is the primary, but the wording can be customised by the author. Lets just leave it as "abort" for now for the secondary, and revisit later to avoid bike-shedding.

michaelneale one observation about the input. In the above input pause the classic UI will display 2 buttons (even if if one is not defined in the above response)

You find there is only "ok" but no "cancel" should we fix this in the backend for consistency, since I could imagine use cases that have only one button, but we could create a "dummy" cancel button if we have only one button.

current testing pipe:

node {
    stage("one"){
        input message: 'Another Brother', ok: 'OK-Computer', parameters: [choice(choices: 'die\nby\nmy\nhand', description: '''stirb
durch
meine
hand''', name: 'choose'), booleanParam(defaultValue: false, description: 'aaaa', name: 'boolena')]

    }
    stage("two"){
      def branchInput = input message: 'Please input branch to test against', parameters: [[$class: 'StringParameterDefinition', defaultValue: 'master', description: '', name: 'branch']]
            echo "BRANCH NAME: ${branchInput}"
    }
}

Input gone wild pipe https://issues.jenkins-ci.org/browse/JENKINS-38494?focusedCommentId=280198&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-280198

tscherler our "Abort" button will be in the header where "stop" and "re-run" usually goes. The "Submit" button should be labeled "Continue".

jamesdumay you are talking about the new design. IMO we should place them correctly when we generally implement the new headers but not in this PR

Just re-read your command. You refer to the dialog where we have the default "cancel" button and the ok which can contain custom caption

tscherler after talking with brody, we think that if there are 5 or less items in a "choice" - use radio button. if there are more than 5, use a drop down.

EDIT: see brody screen shot below.

2 - 6 choices – radio
7+ – dropdown

TODO: brody to confirm colours. Also - no need to add an element for credentials at this stage. Vivek to provide flowNode that can be posted to.

tscherler I had a poke around but didn't find a teal colour in any of the variables.less files on Github.
Either way, they current teal is #24B0D5;