Uploaded image for project: 'Jenkins'
  1. Jenkins
  2. JENKINS-39303

Enhance Input Text Box type for ActiveChoice Reference parameter

    XMLWordPrintable

    Details

    • Similar Issues:

      Description

      The current Input Text Box is limited in several ways.

      • The text box is too small to display most messages.
      • The text box is not editable
      • The value is not passed to the build
        As a result, I rarely use this return type. I opt for a formatted HTML Input Text return type that is larger, editable and can be returned to the build.I think that we should enhance the Input Text Box option to deliver the functionality of the Formatted HTML Input Text without the user having to format the HTML return string and click on the Advanced Option-'Omit Value Field'

        Attachments

          Activity

          Hide
          kinow Bruno P. Kinoshita added a comment -

          Hi Ioannis,

          Agree with your points. I had opened Eclipse to quickly fix and push this change, then I realized that for some reason I had made the input box readonly... here's where it gets interesting

          The value is hidden. An HTML element, with the value. We can omit that element, and then specify our own value.

          Right now the behavior for that element is the following:

          • Return a static HTML element
          • Put the value hidden next to the element, unless user asks to omit it

          Changing the element style to be bigger, and editable; the other HTML element with the value would still be the one dictating what is the parameter value. Unless the user chose to omit the value.

          I think that could be misleading to users. They would have an editable-by-default element, that is not really working as expected (by default we do not omit the value).

          Any thoughts or alternative suggestions?

          Show
          kinow Bruno P. Kinoshita added a comment - Hi Ioannis, Agree with your points. I had opened Eclipse to quickly fix and push this change, then I realized that for some reason I had made the input box readonly... here's where it gets interesting The value is hidden. An HTML element, with the value. We can omit that element, and then specify our own value. Right now the behavior for that element is the following: Return a static HTML element Put the value hidden next to the element, unless user asks to omit it Changing the element style to be bigger, and editable; the other HTML element with the value would still be the one dictating what is the parameter value. Unless the user chose to omit the value. I think that could be misleading to users. They would have an editable-by-default element, that is not really working as expected (by default we do not omit the value). Any thoughts or alternative suggestions?
          Hide
          ioannis Ioannis Moutsatsos added a comment -

          Bruno P. Kinoshita Thanks for trying to explain. Never thought it was so complex. I'm still confused. But I inspected the parameter, and I do see the two inputs. One 'read-only' and one without value. I still don't see the returned value in either. You'll have to explain to me the design.

          Show
          ioannis Ioannis Moutsatsos added a comment - Bruno P. Kinoshita Thanks for trying to explain. Never thought it was so complex. I'm still confused. But I inspected the parameter, and I do see the two inputs. One 'read-only' and one without value. I still don't see the returned value in either. You'll have to explain to me the design.

            People

            • Assignee:
              kinow Bruno P. Kinoshita
              Reporter:
              ioannis Ioannis Moutsatsos
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated: