starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-11 21:10:29 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Filter tab: Custom fields are not grouped #11130

New Issue
Closed
opened 2025-12-29 21:40:43 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:40:43 +01:00
Owner
Copy Link

Originally created by @mathieumd on GitHub (May 6, 2025).

Originally assigned to: @jnovinger on GitHub.

Deployment Type

Self-hosted

NetBox Version

v4.3.0

Python Version

3.12

Steps to Reproduce

  1. Create several custom fields, grouped by several groups, assigned to Virtual Machines
  2. Go to https://netbox.siaga.re/virtualization/virtual-machines/
  3. Open Filters tab
  4. Scroll down to Custom Fields

Expected Behavior

CF should be grouped just like they are when you see or edit a VM (here, groups GLPI and VM):

Image

Observed Behavior

They are not grouped, so you cannot tell exactly what are these ID or Folder:

Image

Originally created by @mathieumd on GitHub (May 6, 2025). Originally assigned to: @jnovinger on GitHub. ### Deployment Type Self-hosted ### NetBox Version v4.3.0 ### Python Version 3.12 ### Steps to Reproduce 1. Create several custom fields, grouped by several groups, assigned to *Virtual Machines* 2. Go to https://netbox.siaga.re/virtualization/virtual-machines/ 3. Open *Filters* tab 4. Scroll down to *Custom Fields* ### Expected Behavior CF should be grouped just like they are when you see or edit a VM (here, groups GLPI and VM): ![Image](https://github.com/user-attachments/assets/e2c11a7a-951f-4c64-8075-dd05c5b8a250) ### Observed Behavior They are not grouped, so you cannot tell exactly what are these *ID* or *Folder*: ![Image](https://github.com/user-attachments/assets/67a1e628-20af-4b58-a0d1-8aa5c93685dd)
adam added the type: bugstatus: acceptedseverity: low labels 2025-12-29 21:40:43 +01:00
adam closed this issue 2025-12-29 21:40:43 +01:00
adam commented 2025-12-29 21:40:44 +01:00
Author
Owner
Copy Link

@arthanson commented on GitHub (May 6, 2025):

This is probably more of a feature request but will leave it as a bug as it is arguable. This would be a generic change for all object display of custom fields in the filter tab.

@arthanson commented on GitHub (May 6, 2025): This is probably more of a feature request but will leave it as a bug as it is arguable. This would be a generic change for all object display of custom fields in the filter tab.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
beta
breaking change
complexity: high
complexity: low
complexity: medium
needs milestone
netbox
pending closure
plugin candidate
pull-request
Mirrored from GitHub Pull Request
 severity: high
severity: low
severity: medium
status: accepted
status: backlog
status: blocked
status: duplicate
status: needs owner
status: needs triage
status: revisions needed
status: under review
topic: GraphQL
topic: Internationalization
topic: OpenAPI
topic: UI/UX
topic: cabling
topic: event rules
topic: htmx navigation
topic: industrialization
topic: migrations
topic: plugins
topic: scripts
topic: templating
topic: testing
type: bug
type: deprecation
type: documentation
type: feature
type: housekeeping
type: translation
No Label severity: low status: accepted type: bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/netbox#11130
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?