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 "max depth" functionality to child prefix pages #9079

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

Originally created by @craigmcfly on GitHub (Jan 11, 2024).

NetBox version

v3.7.0

Feature type

New functionality

Proposed functionality

On /ipam/prefixes/ you can choose the max depth that you want to see.

This would be useful on child pages, i.e. /ipam/prefixes/XXX/prefixes/ to avoid having to look at pages of /31s to see usage.

Use case

I have several /24s broken down into /25s, then so on until /31s for point-to-points. I don't want to have to scroll through pages of /31s to look at just the /25s.

Database changes

No response

External dependencies

No response

Originally created by @craigmcfly on GitHub (Jan 11, 2024). ### NetBox version v3.7.0 ### Feature type New functionality ### Proposed functionality On /ipam/prefixes/ you can choose the max depth that you want to see. This would be useful on child pages, i.e. /ipam/prefixes/XXX/prefixes/ to avoid having to look at pages of /31s to see usage. ### Use case I have several /24s broken down into /25s, then so on until /31s for point-to-points. I don't want to have to scroll through pages of /31s to look at just the /25s. ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 20:45:09 +01:00
adam closed this issue 2025-12-29 20:45:09 +01:00
adam commented 2025-12-29 20:45:09 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 11, 2024):

This idea was proposed in #13197 but did not find anyone interested in implementing it. @craigmcfly would you like to volunteer to own this work?

@jeremystretch commented on GitHub (Jan 11, 2024): This idea was proposed in #13197 but did not find anyone interested in implementing it. @craigmcfly would you like to volunteer to own this work?
adam commented 2025-12-29 20:45:11 +01:00
Author
Owner
Copy Link

@craigmcfly commented on GitHub (Jan 11, 2024):

This idea was proposed in #13197 but did not find anyone interested in implementing it. @craigmcfly would you like to volunteer to own this work?

I'm afraid I lack any sort of technical skill to be able to implement anything.

@craigmcfly commented on GitHub (Jan 11, 2024): > This idea was proposed in #13197 but did not find anyone interested in implementing it. @craigmcfly would you like to volunteer to own this work? I'm afraid I lack any sort of technical skill to be able to implement anything.
adam commented 2025-12-29 20:45:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 12, 2024):

Unfortunately without anyone willing to own the work we'll have to keep this closed. We'll be happy to re-open the FR in the event a volunteer steps up.

@jeremystretch commented on GitHub (Jan 12, 2024): Unfortunately without anyone willing to own the work we'll have to keep this closed. We'll be happy to re-open the FR in the event a volunteer steps up.
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 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#9079
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?