Project

General

Profile

Actions

Bug #3718

closed

List of available Techniques version should be sorted by version number

Added by Jonathan CLARKE over 11 years ago. Updated over 11 years ago.

Status:
Released
Priority:
1 (highest)
Category:
Web - Config management
Target version:
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

1.png (19.7 KB) 1.png Jonathan CLARKE, 2013-07-12 11:28
Actions #1

Updated by Jonathan CLARKE over 11 years ago

Oops, forgot the screenshot.

Actions #2

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!

Actions #3

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
Actions #4

Updated by François ARMAND over 11 years ago

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100
Actions #6

Updated by Nicolas CHARLES over 11 years ago

awesome !

Actions #7

Updated by Nicolas PERRON over 11 years ago

  • Status changed from Pending release to Released
Actions

Also available in: Atom PDF