Actions
Bug #6143
closedRule details text can be misleading
Added by Benoît PECCATTE over 9 years ago. Updated over 7 years ago.
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
In the rule details page > edit parameters, we describe the groups as
"Apply to Nodes in any of these Groups" and "Don't apply to Nodes in any of these Groups"
This is not true since a node can be in both category, in which case we don't know what will happen.
Since it's the "don't apply" that takes precedence, I would like to change the text to
"But not to Nodes in any of these Groups" or "Except to Nodes in any of these Groups"
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.9 to 2.10.10
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.10 to 2.10.11
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.11 to 2.10.12
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.12 to 2.10.13
Updated by Vincent MEMBRÉ over 9 years ago
- Target version changed from 2.10.13 to 2.10.14
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.14 to 2.10.15
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.15 to 2.10.16
Updated by Vincent MEMBRÉ about 9 years ago
- Target version changed from 2.10.16 to 2.10.17
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.17 to 2.10.18
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.18 to 2.10.19
Updated by Vincent MEMBRÉ almost 9 years ago
- Target version changed from 2.10.19 to 2.10.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.10.20 to 277
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 277 to 2.11.18
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.18 to 2.11.19
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.19 to 2.11.20
Updated by Vincent MEMBRÉ over 8 years ago
- Target version changed from 2.11.20 to 2.11.21
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.21 to 2.11.22
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.22 to 2.11.23
Updated by Vincent MEMBRÉ about 8 years ago
- Target version changed from 2.11.23 to 2.11.24
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 2.11.24 to 308
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 308 to 3.1.14
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.14 to 3.1.15
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.15 to 3.1.16
Updated by Vincent MEMBRÉ almost 8 years ago
- Target version changed from 3.1.16 to 3.1.17
Updated by Benoît PECCATTE almost 8 years ago
- Assignee set to Raphael GAUTHIER
- Target version changed from 3.1.17 to 4.1.0~beta1
Updated by Raphael GAUTHIER over 7 years ago
- Status changed from New to In progress
Updated by Raphael GAUTHIER over 7 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
- Pull Request set to https://github.com/Normation/rudder/pull/1381
Updated by Anonymous over 7 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset rudder|0d08ecf84c6c9096b7057516f8a3913e087d4e00.
Updated by Vincent MEMBRÉ over 7 years ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 4.1.0 which was released today.
- 4.1.0: Announce Changelog
- Download: https://www.rudder-project.org/site/get-rudder/downloads/
Actions