Actions
Bug #22702
closedWhen we clone a group in Rudder 7.2, newly added properties are not cloned
Status:
Released
Priority:
N/A
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I hate Rudder for that
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Small
Priority:
145
Name check:
To do
Fix check:
Checked
Regression:
No
Description
If you clone a group, its properties are cloned.
But if you:
- go to a group,
- add a property "newProp"
- clone it
Then "newProp" is not part of the clone while other are.
On contrary, if you:
- go to a group
- add a new property
- reload page with f5
- clone group
Then all properties are present.
So it seems that the JS and backend are not correctly sync-up when we add a property.
Files
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.6 to 7.2.7
Updated by François ARMAND over 1 year ago
- Severity set to Major - prevents use of part of Rudder | no simple workaround
- UX impact set to I hate Rudder for that
- User visibility set to Operational - other Techniques | Rudder settings | Plugins
- Effort required set to Very Small
- Priority changed from 0 to 161
Updated by François ARMAND over 1 year ago
- Status changed from New to In progress
- Assignee set to François ARMAND
Updated by François ARMAND over 1 year ago
- Subject changed from When we clone a group in Rudder 7.2, the properties are not cloned to When we clone a group in Rudder 7.2, newly added properties are not cloned
- Description updated (diff)
- Status changed from In progress to New
- Assignee deleted (
François ARMAND)
Updated by François ARMAND over 1 year ago
- Effort required changed from Very Small to Small
- Priority changed from 161 to 148
Updated by Raphael GAUTHIER over 1 year ago
- Status changed from New to In progress
Updated by Raphael GAUTHIER over 1 year ago
- Status changed from In progress to New
Updated by Vincent MEMBRÉ over 1 year ago
- Target version changed from 7.2.7 to 7.2.8
Updated by Elaad FURREEDAN over 1 year ago
- Status changed from New to In progress
- Assignee changed from Raphael GAUTHIER to Elaad FURREEDAN
- Priority changed from 148 to 146
Updated by Elaad FURREEDAN over 1 year ago
- Status changed from In progress to Pending technical review
- Assignee changed from Elaad FURREEDAN to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/4829
Updated by Elaad FURREEDAN over 1 year ago
- Assignee changed from Nicolas CHARLES to Raphael GAUTHIER
Updated by Elaad FURREEDAN over 1 year ago
- Assignee changed from Raphael GAUTHIER to Nicolas CHARLES
Updated by Elaad FURREEDAN over 1 year ago
- Assignee changed from Nicolas CHARLES to Raphael GAUTHIER
Updated by Anonymous over 1 year ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|ab454592cafcc4fffa0ac3c68bdad84486c44fdc.
Updated by François ARMAND over 1 year ago
- File clipboard-202306291506-46iby.png clipboard-202306291506-46iby.png added
- Priority changed from 146 to 145
- Fix check changed from To do to Checked
Tested in 7.2, works
Updated by Vincent MEMBRÉ over 1 year ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 7.2.8 and 7.3.3 which were released today.
Actions