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

Limit Selection w/ Cable Rear Ports #3891

New Issue
Closed
opened 2025-12-29 18:31:49 +01:00 by adam · 3 comments
adam commented 2025-12-29 18:31:49 +01:00
Owner
Copy Link

Originally created by @iunderwood on GitHub (Jul 23, 2020).

Environment

  • Python version: 3.6.8
  • NetBox version: 2.8.8

Proposed Functionality

When connecting rear ports, after picking my B-Side site and B-Side rack, limit the pull-down selection of devices to ones which only have an available rear port, instead of all the devices in a rack.

This could be automatic, or it could be an option to toggle the view limit.

Use Case

This makes selection a little cleaner. I have a fiber plant I am modeling, which will have over 100 devices in some racks. It would be nice to not see the devices with bays (which have no rear ports), as well as not see device where I have already connected the rear ports.

Database Changes

None required. This should be a limit to the selection criteria.

External Dependencies

None I am aware of.

Originally created by @iunderwood on GitHub (Jul 23, 2020). ### Environment * Python version: 3.6.8 * NetBox version: 2.8.8 ### Proposed Functionality When connecting rear ports, after picking my B-Side site and B-Side rack, limit the pull-down selection of devices to ones which only have an available rear port, instead of all the devices in a rack. This could be automatic, or it could be an option to toggle the view limit. ### Use Case This makes selection a little cleaner. I have a fiber plant I am modeling, which will have over 100 devices in some racks. It would be nice to not see the devices with bays (which have no rear ports), as well as not see device where I have already connected the rear ports. ### Database Changes None required. This should be a limit to the selection criteria. ### External Dependencies None I am aware of.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 18:31:49 +01:00
adam closed this issue 2025-12-29 18:31:49 +01:00
adam commented 2025-12-29 18:31:50 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

Implementing this would require introducing new filters for the devices API endpoint; something like has_available_rear_ports=True. I'm not sure off the top of my head how feasible that is, but it would require a separate feature request.

@jeremystretch commented on GitHub (Jul 24, 2020): Implementing this would require introducing new filters for the devices API endpoint; something like `has_available_rear_ports=True`. I'm not sure off the top of my head how feasible that is, but it would require a separate feature request.
adam commented 2025-12-29 18:31:50 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 12, 2020):

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. Please see our contributing guide.

@stale[bot] commented on GitHub (Sep 12, 2020): 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. Please see our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md).
adam commented 2025-12-29 18:31:50 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Sep 28, 2020):

This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.

@stale[bot] commented on GitHub (Sep 28, 2020): This issue has been automatically closed due to lack of activity. In an effort to reduce noise, please do not comment any further. Note that the core maintainers may elect to reopen this issue at a later date if deemed necessary.
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 pending closure status: needs owner 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#3891
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?