Actions
Bug #3718
closedList of available Techniques version should be sorted by version number
Status:
Released
Priority:
1 (highest)
Assignee:
Category:
Web - Config management
Target version:
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
See this, in the Directives screen, after clicking on a Technique ("Package management for RHEL / CentOS / SuSE / RPM systems" in this case):
This list of versions should be sorted by version number, backwards, so 4.0, 3.0, 2.2, 2.1, 2.0, 1.0.
Files
Updated by Jonathan CLARKE over 11 years ago
Oops, forgot the screenshot.
Updated by Jonathan CLARKE over 11 years ago
- Priority changed from 3 to 1 (highest)
This actually seems worse than I originally imagined: when you create a Directive, it is no longer created in the latest version (version 1.0 for a Technique with 6 versions, in my test above).
This needs urgent attention!
Updated by François ARMAND over 11 years ago
- Status changed from 8 to Pending technical review
- Assignee changed from François ARMAND to Nicolas CHARLES
- Pull Request set to https://github.com/Normation/rudder/pull/257
Technical review here: https://github.com/Normation/rudder/pull/257
Updated by François ARMAND over 11 years ago
- Status changed from Pending technical review to Pending release
- % Done changed from 0 to 100
Applied in changeset ef1b992595f4b24537ea0e3352f89c8843699647.
Updated by Nicolas CHARLES over 11 years ago
Applied in changeset f869074a2c7bdbb0b29b52cba96565cec536f135.
Updated by Nicolas PERRON over 11 years ago
- Status changed from Pending release to Released
Actions