Bug #18718
Saving a boolean matcher with no value changes the value to false
| Status: | Closed | ||
|---|---|---|---|
| Priority: | Normal | ||
| Assigned To: |  Ori Rabin | ||
| Category: | Smart Variables | ||
| Target version: | Team Ivan Iteration 11 | ||
| Difficulty: | Bugzilla link: | ||
| Found in release: | Pull request: | https://github.com/theforeman/foreman/pull/4345 | |
| Story points | - | ||
| Velocity based estimate | - | ||
| Release | 1.14.3 | Release relationship | Auto |
Related issues
Associated revisions
Fixes #18718 - Empty boolean matcher should not turn into false
Fixes #18718 - Empty boolean matcher should not turn into false
(cherry picked from commit 100cf25b86366d1646e8221ebcfb21750c353548)
History
#1
Updated by Ori Rabin about 1 year ago
- Related to Bug #17870: Saving an empty matcher for smart class parameter of type boolean saves the value false added
#2
Updated by Ori Rabin about 1 year ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset 100cf25b86366d1646e8221ebcfb21750c353548.
#3
Updated by Ivan Necas about 1 year ago
- Target version set to Team Ivan Iteration 11
#4
Updated by Dominic Cleal about 1 year ago
- Release set to 1.14.3