Actions
Bug #3732
closedMigration of some Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Status:
Released
Priority:
2
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
If I migrate a directive (in this case I tried to migrate user management from 1.0 to 2.0) I'm required to save the form afterwards. However, the message " There are no modification to save" appears and the directive hasn't been migrated. Workaround is to change anything in the form, migrate, save and then change it back.
Updated by François ARMAND over 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/279
Updated by François ARMAND over 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Updated by Nicolas PERRON over 11 years ago
- Subject changed from Migrate directive: There are no modification to save to Migration of Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Updated by Nicolas PERRON over 11 years ago
- Subject changed from Migration of Directives version does not work if no modification are made in the parameters with the message "There are no modification to save" to Migration of some Directives version does not work if no modification are made in the parameters with the message "There are no modification to save"
Updated by Benoît PECCATTE about 10 years ago
- Category changed from 14 to Web - Config management
Actions