Project

General

Profile

Actions

User story #11725

closed

Change how Directive priority is displayed

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

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
UX impact:
Suggestion strength:
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Very Small
Name check:
Fix check:
Regression:

Description

In directives, we have a "priority" field that allows to choose what directive must be chosen for a non-multi instance technique.

That field is a select with choices: [0,1,2,3...,10]

And 0 is the most prioritary, ie the one directive that get chosen. Appart from some computer scientist using cons list all day, this is strange.

We need to change that to something more understandable. I propose:

Priority: 

[ default ]
 ---------
| highest |
| +4      |
| +3      |
| +2      |
| +1      |
| default |
| -1      |
| -2      |
| -3      |
| -4      |
| lowest  |
 ---------

Of course, in the backend and database, nothing change (ie we still map toward integers from 0 to 10, most prioriterary = 0)


Files

Actions #1

Updated by François ARMAND over 6 years ago

  • Status changed from New to In progress
  • Assignee set to François ARMAND
Actions #2

Updated by François ARMAND over 6 years ago

  • Description updated (diff)

Change order to put "highest" on top

Actions #4

Updated by François ARMAND over 6 years ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from François ARMAND to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1778
Actions #5

Updated by Vincent MEMBRÉ over 6 years ago

  • Subject changed from "Priority" level mean the contrary to what is thought to Change how Directive priority is displayed
Actions #6

Updated by Vincent MEMBRÉ over 6 years ago

  • Tracker changed from Bug to User story
Actions #7

Updated by François ARMAND over 6 years ago

  • Status changed from Pending technical review to Pending release
Actions #8

Updated by Vincent MEMBRÉ over 6 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 4.1.9 and 4.2.3 which were released today.

Actions

Also available in: Atom PDF