Actions
Bug #18049
closed
Impossible to define group properties in group of groups
Status:
Resolved
Priority:
N/A
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Very Small
Priority:
0
Name check:
To do
Fix check:
To do
Regression:
No
Description
When having a conflict of groups properties (ie: 2 groups without common parents that define the same keys, and are applied to a common node)
a good solution is to define a group of group to resolve this conflict for this specific case.
It works well, but then, this new group can not define nor retrieve its own properties. I always end up with an error message when visiting its page in the UI.
Also, I can not see nor define new properties for this group.
Files
| error_group.png (43.1 KB) error_group.png | |||
| clipboard-202303091746-gm3im.png (69.7 KB) clipboard-202303091746-gm3im.png | |||
| clipboard-202303091747-9d2vg.png (62.9 KB) clipboard-202303091747-9d2vg.png |
Updated by 
Updated by François ARMAND over 3 years ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 80
Updated by François ARMAND over 3 years ago
- Target version changed from 6.1.3 to 6.1.4
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.4 to 6.1.5
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.5 to 6.1.6
- Priority changed from 80 to 79
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.6 to 6.1.7
- Priority changed from 79 to 78
Updated by François ARMAND over 3 years ago
- Related to User story #16347: Group properties added
Updated by Vincent MEMBRÉ over 3 years ago
- Target version changed from 6.1.7 to 6.1.8
- Priority changed from 78 to 76
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.8 to 6.1.9
- Priority changed from 76 to 75
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.9 to 6.1.10
- Priority changed from 75 to 74
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.10 to 6.1.11
- Priority changed from 74 to 72
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.11 to 6.1.12
Updated by Vincent MEMBRÉ about 3 years ago
- Target version changed from 6.1.12 to 6.1.13
- Priority changed from 72 to 71
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.13 to 6.1.14
- Priority changed from 71 to 70
Updated by Vincent MEMBRÉ almost 3 years ago
- Target version changed from 6.1.14 to 6.1.15
- Priority changed from 70 to 68
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.15 to 6.1.16
- Priority changed from 68 to 67
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.16 to 6.1.17
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.17 to 6.1.18
Updated by Vincent MEMBRÉ over 2 years ago
- Target version changed from 6.1.18 to 6.1.19
Updated by Vincent MEMBRÉ about 2 years ago
- Target version changed from 6.1.19 to 6.1.20
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.20 to 6.1.21
Updated by Vincent MEMBRÉ almost 2 years ago
- Target version changed from 6.1.21 to old 6.1 issues to relocate
Actions
#25
Updated by François ARMAND about 1 year ago
- File clipboard-202303091746-gm3im.png clipboard-202303091746-gm3im.png added
- File clipboard-202303091747-9d2vg.png clipboard-202303091747-9d2vg.png added
- Status changed from New to Resolved
- Priority changed from 67 to 0
- Regression set to No
It's working in 7.2 
Actions