Actions
Bug #27580
open
Nodes properties cannot be exported to CSV
Status:
New
Priority:
1 (highest)
Assignee:
Category:
Web - Nodes & inventories
Target version:
Pull Request:
Severity:
Major - prevents use of part of Rudder | no simple workaround
UX impact:
I dislike using that feature
User visibility:
First impressions of Rudder
Effort required:
Small
Priority:
139
Name check:
To do
Fix check:
To do
Regression:
No
Description
The value of the property in the CSV export is always N/A, even if the property belongs to the node.
We should export the property value in the CSV (treat each property as a specific column, just like for "compliance", see #467).
For inherited properties we may also want to export the inherited ones.
We should export the correct value of overridden property if it is overridden
Files
| clipboard-202509161610-xjdjx.png (124 KB) clipboard-202509161610-xjdjx.png | |||
| clipboard-202509161611-unbwa.png (20.7 KB) clipboard-202509161611-unbwa.png |
Updated by Clark ANDRIANASOLO 2 days ago
- Related to User story #467: CSV export of server list (simple) added
Updated by Clark ANDRIANASOLO 2 days ago
- Target version changed from 9.0.0~beta2 to 8.3.5
Updated by Clark ANDRIANASOLO 2 days ago
The fix may be obsolete when we migrate the table in Elm in upper versions, since the Elm implementation would be different
Updated by Nicolas CHARLES 7 minutes ago
- Severity changed from Minor - inconvenience | misleading | easy workaround to Major - prevents use of part of Rudder | no simple workaround
- Priority changed from 120 to 139
Updated by François ARMAND 5 minutes ago
- Assignee set to Vincent MEMBRÉ
- Priority changed from To review to 1 (highest)
Actions