Bug #24627
closedWe can add the same score details column many times in nodes tables
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
Updated by Clark ANDRIANASOLO 7 months ago
- File clipboard-202403291604-q41le.png clipboard-202403291604-q41le.png added
- Description updated (diff)
Updated by Clark ANDRIANASOLO 6 months ago
- Status changed from New to In progress
- Assignee set to Clark ANDRIANASOLO
Updated by Clark ANDRIANASOLO 6 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
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.0~rc1 to 8.1.0
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.0 to 8.1.1
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.1 to 8.1.2
Updated by Vincent MEMBRÉ 6 months ago
- Target version changed from 8.1.2 to 8.1.3
Updated by Vincent MEMBRÉ 5 months ago
- Status changed from Pending technical review to In progress
Updated by Vincent MEMBRÉ 5 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
Updated by Vincent MEMBRÉ 5 months ago
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
Updated by Vincent MEMBRÉ 5 months ago
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
- Priority changed from 108 to 107
Updated by Vincent MEMBRÉ 5 months ago
- Assignee changed from François ARMAND to Clark ANDRIANASOLO
Updated by Vincent MEMBRÉ 5 months ago
- Assignee changed from Clark ANDRIANASOLO to François ARMAND
Updated by Anonymous 5 months ago
- Status changed from Pending technical review to Pending release
Applied in changeset rudder|483798a9358e4028a571d3583bed8267b6ee7eac.
Updated by Clark ANDRIANASOLO 5 months ago
- Related to Bug #24925: Refresh on nodes tables leads to datatable and console error added
Updated by Elaad FURREEDAN 5 months ago
- Priority changed from 107 to 106
- Fix check changed from To do to Checked
Updated by Vincent MEMBRÉ 4 months ago
- Status changed from Pending release to Released
This bug has been fixed in Rudder 8.1.3 which was released today.