Project

General

Profile

Actions
Copy link

Bug #22702

closed

When we clone a group in Rudder 7.2, newly added properties are not cloned

Added by Nicolas CHARLES over 1 year ago. Updated over 1 year ago.

Status:
Released
Priority:
N/A
Assignee:
Raphael GAUTHIER
Category:
Web - Nodes & inventories
Target version:
7.2.8
Pull Request:
https://github.com/Normation/rudder/p...
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

clipboard-202306291506-46iby.png (102 KB) clipboard-202306291506-46iby.png François ARMAND, 2023-06-29 15:06
Actions
Copy link

Also available in: Atom PDF