Project

General

Profile

User story #11725

Change how Directive priority is displayed

Added by François ARMAND 5 months ago. Updated 4 months ago.

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

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)

Associated revisions

Revision e5e0aa4e (diff)
Added by François ARMAND 5 months ago

Fixes #11725: \"Priority\" level mean the contrary to what is thought

Revision 78c03612 (diff)
Added by François ARMAND 5 months ago

Fixes #11725: \"Priority\" level mean the contrary to what is thought

History

#1 Updated by François ARMAND 5 months ago

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

#2 Updated by François ARMAND 5 months ago

  • Description updated (diff)

Change order to put "highest" on top

#4 Updated by François ARMAND 5 months 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

#5 Updated by Vincent MEMBRÉ 5 months ago

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

#6 Updated by Vincent MEMBRÉ 5 months ago

  • Tracker changed from Bug to User story

#7 Updated by François ARMAND 5 months ago

  • Status changed from Pending technical review to Pending release

#8 Updated by Vincent MEMBRÉ 4 months 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.

Also available in: Atom PDF