Actions
Bug #21515
closed
result condition are not correct in the technique editor when using properties or variables
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Technique editor
Target version:
Pull Request:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Priority:
80
Name check:
To do
Fix check:
Checked
Regression:
No
Description
with ${node.properties[package]}, the result is 
with ${node.properties}, the result is
which is totally invalid
valid in 6.2, broken in 7.0 and 7.1
Files
Updated by Nicolas CHARLES over 2 years ago
- Target version changed from 7.1.4 to 7.0.6
Updated by Nicolas CHARLES over 2 years ago
- Status changed from New to In progress
- Assignee set to Nicolas CHARLES
Updated by François ARMAND over 2 years ago
- Severity set to Minor - inconvenience | misleading | easy workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Priority changed from 0 to 80
Updated by Nicolas CHARLES over 2 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Nicolas CHARLES to François ARMAND
- Pull Request set to https://github.com/Normation/rudder/pull/4408
Updated by Nicolas CHARLES over 2 years ago
- Priority changed from 80 to 104
- Regression set to Yes
Updated by Nicolas CHARLES over 2 years ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|bb6229521225ffe53a1bced05447a49ae35834f2.
Updated by Alexis Mousset over 2 years ago
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ about 2 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.0.6 and 7.1.4 which were released today.
Updated by François ARMAND about 2 years ago
- Priority changed from 104 to 80
- Regression changed from Yes to No
Actions