- 
    Improvement 
- 
    Resolution: Fixed
- 
    Minor 
- 
    None
Consider the following workflow script:
echo "bool=$bool"
echo bool.getClass().toString()
Output:
Started by user Jos Backus
Running: Print Message
bool=false
Running: Print Message
class java.lang.String
Running: End of Workflow
Finished: SUCCESS
I would expect the name of the class to be java.lang.Boolean, not java.lang.String. This forces one to add lines such as:
bool = bool == 'true'
- is blocking
- 
                    JENKINS-27413 Handle file parameters -         
- Resolved
 
-         
- is duplicated by
- 
                    JENKINS-27388 Build parameters are injected as typeless strings into workflow script -         
- Resolved
 
-         
- is related to
- 
                    JENKINS-29952 Allow access to environment variables as Groovy variables -         
- Resolved
 
-         
- 
                    JENKINS-30519 Declarative job properties in multibranch -         
- Resolved
 
-         
- 
                    JENKINS-34101 Option for input parameters to be flattened to string -         
- Open
 
-         
- 
                    JENKINS-35698 Initial run of parameterized pipeline build should return properties default value -         
- Resolved
 
-         
- links to
