Project

General

Profile

Bug #10659

Node search input field are tiny and a nightmare to use

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

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Target version (plugin):
Severity:
Minor - inconvenience | misleading | easy workaround
User visibility:
Getting started - demo | first install | level 1 Techniques
Effort required:
Small
Priority:
43

Description

When we are searching for nodes (or creating groups), the value field is tiny, and most of the time we can't even see whole simple value (almost not even a full UUID!) - not speaking for regex.

We need that field to be much bigger by default, and perhaps force the whole value to always be fully displayed (even if it means going one several line - I don't mean textarea here)

Associated revisions

Revision ef83faf1
Added by Raphaël Gauthier 6 months ago

Fixes #10659: Node search input field are tiny and a nightmare to use

History

#1 Updated by Raphael GAUTHIER 7 months ago

  • Status changed from New to In progress

#2 Updated by Jonathan CLARKE 7 months ago

  • Severity changed from Major - prevents use of part of Rudder | no simple workaround to Minor - inconvenience | misleading | easy workaround
  • Priority changed from 72 to 53

Objectively, this does not prevent use, it hinders it, so changing severity to Minor. We must be careful not to abuse severity levels - if we end up one day making some form fields bigger instead of fixing a bug that prevents Rudder working on, for example, SLES (also a Major bug - prevents use of part of Rudder), that would be a serious mistake, and users would blame us for it.

#3 Updated by François ARMAND 7 months ago

Well, you are right.
For post mortem, I set it to major because there was reported problem on groups due to the fact that the whole value was not seen, and so there was a typo between lines leading to a disaster. But for one, I should have tell that in the ticket, and for 2/, objectively it was a user fault and nothing to do with Rudder, which was only misleading. So "minor" is correct.

#4 Updated by Raphael GAUTHIER 7 months ago

  • Status changed from In progress to New
  • Effort required changed from Very Small to Small
  • Priority changed from 53 to 43

#5 Updated by Vincent MEMBRÉ 6 months ago

  • Target version changed from 3.1.20 to 3.1.21

#6 Updated by Benoît PECCATTE 6 months ago

First just enlarge the last column to the width of the page.
And enlarge a little bit the 2nd one.

#7 Updated by Raphael GAUTHIER 6 months ago

  • Status changed from New to Pending technical review
  • Assignee changed from Raphael GAUTHIER to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/1660

#8 Updated by Anonymous 5 months ago

  • Status changed from Pending technical review to Pending release

#9 Updated by Alexis MOUSSET 5 months ago

  • Status changed from Pending release to Released

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

Also available in: Atom PDF