Project

General

Profile

Actions
Copy link

Bug #21503

closed

Unable to sort on property in list of nodes tab

Added by Elaad FURREEDAN over 2 years ago. Updated over 2 years ago.

Status:
Released
Priority:
N/A
Assignee:
François ARMAND
Category:
Web - UI & UX
Target version:
6.2.20
Pull Request:
https://github.com/Normation/rudder/p...
Severity:
Minor - inconvenience | misleading | easy workaround
UX impact:
I dislike using that feature
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
70
Name check:
To do
Fix check:
Checked
Regression:
No

Description

When we add the column "Property" in the list of nodes tab, the sort doesn't do anything, we should at least be able to sort when value is a string

Related issues 1 (0 open — 1 closed)

Related to Rudder - Bug #22092: Deleting custom column in based on a property in nodes list failsReleasedFrançois ARMANDActions
Actions
Copy link
 #1

Updated by Elaad FURREEDAN over 2 years ago

  • Severity set to Minor - inconvenience | misleading | easy workaround
  • UX impact set to I dislike using that feature
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Priority changed from 0 to 89
Actions
Copy link
 #2

Updated by Elaad FURREEDAN over 2 years ago

  • Effort required set to Medium
  • Priority changed from 89 to 72
Actions
Copy link
 #3

Updated by Nicolas CHARLES over 2 years ago

  • Regression set to No

replacing the content of the cell with plain text doesn't solve the issue

Actions
Copy link
 #4

Updated by Nicolas CHARLES over 2 years ago

in the "data" object, the value is always N/A

Actions
Copy link
 #5

Updated by Nicolas CHARLES over 2 years ago

in the oData, the entry is an object, that's why it doesn't sort (and maybe that's why it doesn't show in the data also)

Actions
Copy link
 #6

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.17 to 997
Actions
Copy link
 #7

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 997 to 6.2.18
Actions
Copy link
 #8

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.18 to 6.2.19
Actions
Copy link
 #9

Updated by Vincent MEMBRÉ over 2 years ago

  • Target version changed from 6.2.19 to 6.2.20
Actions
Copy link
 #10

Updated by Vincent MEMBRÉ over 2 years ago

  • Status changed from New to In progress
  • Assignee set to Vincent MEMBRÉ
  • Priority changed from 72 to 71
Actions
Copy link
 #11

Updated by Vincent MEMBRÉ over 2 years ago

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

Updated by Vincent MEMBRÉ over 2 years ago

  • Status changed from Pending technical review to Pending release
Actions
Copy link
 #13

Updated by Vincent MEMBRÉ over 2 years ago

  • Priority changed from 71 to 70
  • Fix check changed from To do to Checked
Actions
Copy link
 #14

Updated by Vincent MEMBRÉ over 2 years ago

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 6.2.20, 7.1.7 and 7.2.1 which were released today.

Actions
Copy link
 #15

Updated by Vincent MEMBRÉ over 2 years ago

  • Related to Bug #22092: Deleting custom column in based on a property in nodes list fails added
Actions
Copy link

Also available in: Atom PDF