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

Add rack as filter option to rack elevation #7517

New Issue
Closed
opened 2025-12-29 20:24:35 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:24:35 +01:00
Owner
Copy Link

Originally created by @rodvand on GitHub (Jan 15, 2023).

Originally assigned to: @arthanson on GitHub.

NetBox version

v3.4.2

Feature type

New functionality

Proposed functionality

In the rack elevation filter section add rack as a multiple input choice field.

Use case

If you want to "compare" single racks to each other. It is possible today with using ?id=x&id=y in the URL but it would be nice to have this feature as a field in the filter section.

Database changes

None

External dependencies

None

Originally created by @rodvand on GitHub (Jan 15, 2023). Originally assigned to: @arthanson on GitHub. ### NetBox version v3.4.2 ### Feature type New functionality ### Proposed functionality In the rack elevation filter section add rack as a multiple input choice field. ### Use case If you want to "compare" single racks to each other. It is possible today with using ?id=x&id=y in the URL but it would be nice to have this feature as a field in the filter section. ### Database changes None ### External dependencies None
adam added the status: acceptedtype: feature labels 2025-12-29 20:24:35 +01:00
adam closed this issue 2025-12-29 20:24:35 +01:00
adam commented 2025-12-29 20:24:36 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Jan 16, 2023):

As the id is exposed in the d7c37d9dd6/netbox/dcim/forms/filtersets.py (L300-L309) we can add the functionality by copying the d7c37d9dd6/netbox/dcim/forms/filtersets.py (L225-L233) from RackFilterForm and add id on line d7c37d9dd6/netbox/dcim/forms/filtersets.py (L226)
as this: (None, ('q', 'filter_id', 'tag', 'id')),

It's not very DRY so if there is any other way of making this more dynamic I'm open for suggestions...

@rodvand commented on GitHub (Jan 16, 2023): As the id is exposed in the https://github.com/netbox-community/netbox/blob/d7c37d9dd6556654dcfa9ec940c3f1af9d4d3c6e/netbox/dcim/forms/filtersets.py#L300-L309 we can add the functionality by copying the https://github.com/netbox-community/netbox/blob/d7c37d9dd6556654dcfa9ec940c3f1af9d4d3c6e/netbox/dcim/forms/filtersets.py#L225-L233 from `RackFilterForm` and add id on line https://github.com/netbox-community/netbox/blob/d7c37d9dd6556654dcfa9ec940c3f1af9d4d3c6e/netbox/dcim/forms/filtersets.py#L226 as this: `(None, ('q', 'filter_id', 'tag', 'id')),` It's not very DRY so if there is any other way of making this more dynamic I'm open for suggestions...
adam commented 2025-12-29 20:24:37 +01:00
Author
Owner
Copy Link

@rodvand commented on GitHub (Jan 27, 2023):

I haven't run the feature branch to test, but will https://github.com/netbox-community/netbox/issues/11598 cover this FR @jeremystretch ? Having to go from the rack list to elevations isn't a big deal for me.

@rodvand commented on GitHub (Jan 27, 2023): I haven't run the feature branch to test, but will https://github.com/netbox-community/netbox/issues/11598 cover this FR @jeremystretch ? Having to go from the rack list to elevations isn't a big deal for me.
adam commented 2025-12-29 20:24:38 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 28, 2023):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. Do not attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our contributing guide.

@github-actions[bot] commented on GitHub (Apr 28, 2023): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. NetBox is governed by a small group of core maintainers which means not all opened issues may receive direct feedback. **Do not** attempt to circumvent this process by "bumping" the issue; doing so will result in its immediate closure and you may be barred from participating in any future discussions. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
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#7517
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?