Actions
Bug #3082
closed
Cloning Directives is not intuitive in the UI
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
There is several things broken with directive cloning:
- the [Clone] button must go at the top, in the "modify status" zone (which should be renamed "Actions")
- when clickink on [Clone], the pop-up does not contain the "modification message zone". That zone must be added
- when clicking on [Configure] in the pop-up, the cloned directive IS NOT ACTUALLY SAVED. One's has to click AGAIN on save to have the clone. The clone must be created as soon as the pop-up is validated.
Updated by Nicolas PERRON over 11 years ago
- Target version changed from 2.4.2 to 2.4.3
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from 8 to In progress
- Assignee changed from François ARMAND to Vincent MEMBRÉ
I'm on it
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from In progress to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
Pull request here : https://github.com/Normation/rudder/pull/89
Updated by Vincent MEMBRÉ over 11 years ago
Improved (good target branch) Pull request here : https://github.com/Normation/rudder/pull/94
Updated by Vincent MEMBRÉ over 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset 814bab505108ed73beb711b3d75affb808f19b63.
Updated by Anonymous over 11 years ago
Applied in changeset b89e51327f233d01a4867ce26ba365c8a2846824.
Updated by Jonathan CLARKE about 11 years ago
- Subject changed from Cloning directive is broken to Cloning Directives is not intuitive in the UI
Clarifying bug title - this was a UI problem, not a broken feature.
Updated by Nicolas PERRON about 11 years ago
- Status changed from Pending release to Released
Actions