-
Bug
-
Resolution: Not A Defect
-
Major
-
None
-
Active Choices v1.5.3, Jenkins 2.19.2
Using an AC Reference parameter rendered as a complex HTML element. The value of this parameter when passed to the build is different than the value when user is interacting with the build form.
I'm attaching an example project for testing. The complex HTML element generated from the interaction with the form is displayed and is also passed to the build.
You can easily see the disrepancy between these two values after the build is performed by reviewing the build parameters
- is duplicated by
-
JENKINS-69516 HTML-formatted (reactive reference) boolean/checkbox input parameters do not pass on values, only true/false
- Fixed but Unreleased