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

Add fields to components filter #6309

New Issue
Closed
opened 2025-12-29 19:39:13 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:39:13 +01:00
Owner
Copy Link

Originally created by @mmfreitas on GitHub (Apr 6, 2022).

Originally assigned to: @minitriga on GitHub.

NetBox version

v3.2.0

Feature type

Change to existing functionality

Proposed functionality

Currently we have the following component filters:

image

I have noticed that I can't easily filter device types and module types when I want to know if they have device bays or module bays configured. I've been using tags to keep track of this, but I think this should be on the filters tab, so I would propose the addition of the following filter choices:

  • Has Device Bays
  • Has Module Bays
  • Has Inventory Items

Use case

To be able to filter for components that currently are not possible.

Database changes

None.

External dependencies

No response

Originally created by @mmfreitas on GitHub (Apr 6, 2022). Originally assigned to: @minitriga on GitHub. ### NetBox version v3.2.0 ### Feature type Change to existing functionality ### Proposed functionality Currently we have the following component filters: ![image](https://user-images.githubusercontent.com/91552302/162026716-c52dc82c-6484-4a79-8d40-dd00f449f331.png) I have noticed that I can't easily filter device types and module types when I want to know if they have device bays or module bays configured. I've been using tags to keep track of this, but I think this should be on the filters tab, so I would propose the addition of the following filter choices: - Has Device Bays - Has Module Bays - Has Inventory Items ### Use case To be able to filter for components that currently are not possible. ### Database changes None. ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:39:13 +01:00
adam closed this issue 2025-12-29 19:39:13 +01:00
adam commented 2025-12-29 19:39:13 +01:00
Author
Owner
Copy Link

@minitriga commented on GitHub (Apr 15, 2022):

All done

@minitriga commented on GitHub (Apr 15, 2022): All done
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 status: accepted type: feature
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#6309
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?