Project

General

Profile

Actions

Bug #7059

closed

User story #2881: Allow user to choose order of Directive application in a Rule

In UI, directives in a rule are not sorted as their bundle order

Added by François ARMAND over 8 years ago. Updated over 8 years ago.

Status:
Released
Priority:
1
Category:
Web - Config management
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

In the UI, in the rules screen or node screen, rules are not sorted accordingly to the bundle ordre.

More precisely, there is 3 places where rules and directives must be correctly sorted:

- in node details, in report tab: display first all system rules, then rules sorted by name, and for them, directives sorted by name
- in rules, in the list, do not show system rules, and sort user rules by name
- in rule details, sort directive by name in the green zone where enabled directive are listed.

Actions #1

Updated by François ARMAND over 8 years ago

  • Subject changed from In UI, Rules and directives in rules are not sorted as their bundle order to In UI, directives in a rule are not sorted as their bundle order

OK, so in fact:

- in rules array, the rules are already sorted alpha-num,
- in rule details, we have to sort directive,
- and in node details, we can't really sort in a meaning full way the list of rules.

For the last case, what would make sense would be to have two tables, one for use rules (sorted alpha-num), and one for system rules (also sorted).

So this ticket only take care of sorting directive in a rule.

Actions #2

Updated by François ARMAND over 8 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/906
Actions #3

Updated by François ARMAND over 8 years ago

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

Updated by François ARMAND over 8 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 3.1.1 which was released today.

Actions

Also available in: Atom PDF