|
If you were logged in you would be able to see more operations.
|
|
|
QuickBuild
Created: 04/Jan/10 06:38 PM
Updated: 02/Mar/10 02:05 AM
|
|
| Component/s: |
None
|
| Affects Version/s: |
None
|
| Fix Version/s: |
None
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
File Attachments:
|
1.
test-var (3 kb)
|
|
|
Added a variable to a configuration, set it's value to "true", "prompt as selection box", set "allow empty" to be "false", add two choices "true" and "false". Kick off a build, you're prompted for the value of the variable with the value defaulting to being empty. Click "OK" and the build will continue, despite "allow empty" set to "false". This seems broken.
This occured when using QB v2.0.12 (version list above doesn't seem to list any recent v2 versions)
|
|
Description
|
Added a variable to a configuration, set it's value to "true", "prompt as selection box", set "allow empty" to be "false", add two choices "true" and "false". Kick off a build, you're prompted for the value of the variable with the value defaulting to being empty. Click "OK" and the build will continue, despite "allow empty" set to "false". This seems broken.
This occured when using QB v2.0.12 (version list above doesn't seem to list any recent v2 versions) |
Show » |
| No work has yet been logged on this issue.
|
|
Bug
Resolved
Minor
A variable where "allow emtpy" is set to "no" is allowed to be empty