Project

General

Profile

Actions

Bug #24627

closed

We can add the same score details column many times in nodes tables

Added by Clark ANDRIANASOLO 4 months ago. Updated about 1 month ago.

Status:
Released
Priority:
N/A
Category:
Web - UI & UX
Target version:
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
It bothers me each time
User visibility:
First impressions of Rudder
Effort required:
Small
Priority:
106
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When selecting a new column to add in nodes tables, if the column is added it eventually disappears from the list of columns to add.
But when selecting a Score details, and an option e.g. Compliance, when adding it the "select" resets to the first one of the list.
And when selecting another Score details, I can still see Compliance in the choices, even though it is already a column of the table :

We should make the select also behave more consistently :
- we should remove the selection options for Score details columns which are already displayed
- we should keep the Score details selected and choose the first of the remaining choices by default when a score details column is added
- we should remove the Score details option when all are already selected
- (optionally) we should add All to the choices of score details columns. It is likely users would like to have those indicators in the view of all nodes.

N.B. another issue is caused by having duplicate columns and we should really do the fix because it has a very weird behavior :
when adding the same column twice, then removing the duplicate, it appears as a choice in the main selection (at the same level as Score details !), and the rest of the flow seems broken until we refresh the page and discard our changes


Files

clipboard-202403291536-gjlyh.png (39.3 KB) clipboard-202403291536-gjlyh.png Clark ANDRIANASOLO, 2024-03-29 15:36
clipboard-202403291604-q41le.png (38.7 KB) clipboard-202403291604-q41le.png Clark ANDRIANASOLO, 2024-03-29 16:04

Related issues 1 (0 open1 closed)

Related to Rudder - Bug #24925: Refresh on nodes tables leads to datatable and console error ReleasedVincent MEMBRÉActions
Actions #2

Updated by Clark ANDRIANASOLO 3 months ago

  • Status changed from New to In progress
  • Assignee set to Clark ANDRIANASOLO
Actions #3

Updated by Clark ANDRIANASOLO 3 months ago

  • Status changed from In progress to Pending technical review
  • Assignee changed from Clark ANDRIANASOLO to Vincent MEMBRÉ
  • Pull Request set to https://github.com/Normation/rudder/pull/5568
Actions #4

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.0~rc1 to 8.1.0
Actions #5

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.0 to 8.1.1
Actions #6

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.1 to 8.1.2
Actions #7

Updated by Vincent MEMBRÉ 3 months ago

  • Target version changed from 8.1.2 to 8.1.3
Actions #8

Updated by Vincent MEMBRÉ 2 months ago

  • Status changed from Pending technical review to In progress
Actions #9

Updated by Vincent MEMBRÉ 2 months ago

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

Updated by Vincent MEMBRÉ 2 months ago

  • Assignee changed from François ARMAND to Clark ANDRIANASOLO
Actions #11

Updated by Vincent MEMBRÉ about 2 months ago

  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
  • Priority changed from 108 to 107
Actions #12

Updated by Vincent MEMBRÉ about 2 months ago

  • Assignee changed from François ARMAND to Clark ANDRIANASOLO
Actions #13

Updated by Vincent MEMBRÉ about 2 months ago

  • Assignee changed from Clark ANDRIANASOLO to François ARMAND
Actions #14

Updated by Anonymous about 2 months ago

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

Updated by Clark ANDRIANASOLO about 2 months ago

  • Related to Bug #24925: Refresh on nodes tables leads to datatable and console error added
Actions #16

Updated by Elaad FURREEDAN about 2 months ago

  • Priority changed from 107 to 106
  • Fix check changed from To do to Checked
Actions #17

Updated by Vincent MEMBRÉ about 1 month ago

  • Status changed from Pending release to Released

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

Actions

Also available in: Atom PDF