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

Site Prefix List - Bad Indentation #4921

New Issue
Closed
opened 2025-12-29 19:22:17 +01:00 by adam · 5 comments
adam commented 2025-12-29 19:22:17 +01:00
Owner
Copy Link

Originally created by @networkhorse on GitHub (May 18, 2021).

NetBox version

v2.11.3

Python version

3.8

Steps to Reproduce

Create the following structure:
image
image

Assign the deepest prefixes to a site.

Expected Behavior

Hierarchy should be "local", i.e. only relevant to that site's prefixes. It should not show indentation for Netbox as a whole. I expect something like this:
image

Observed Behavior

Prefixes have very misleading indentation, as in the photo below. None of these subnets are related.

image

Originally created by @networkhorse on GitHub (May 18, 2021). ### NetBox version v2.11.3 ### Python version 3.8 ### Steps to Reproduce Create the following structure: ![image](https://user-images.githubusercontent.com/22162629/118674854-0643b000-b7f2-11eb-846d-50a1383d10d0.png) ![image](https://user-images.githubusercontent.com/22162629/118674901-0e035480-b7f2-11eb-9132-2e2287ee7ce6.png) Assign the deepest prefixes to a site. ### Expected Behavior Hierarchy should be "local", i.e. only relevant to that site's prefixes. It should not show indentation for Netbox as a whole. I expect something like this: ![image](https://user-images.githubusercontent.com/22162629/118675699-b6b1b400-b7f2-11eb-9857-30c4b13bb42a.png) ### Observed Behavior Prefixes have very misleading indentation, as in the photo below. None of these subnets are related. ![image](https://user-images.githubusercontent.com/22162629/118675099-3f7c2000-b7f2-11eb-83a4-ab3bb350ba0e.png)
adam closed this issue 2025-12-29 19:22:18 +01:00
adam commented 2025-12-29 19:22:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 18, 2021):

Please update your post above to indicate the specific values for each object being created, so that someone else can try reproducing the reported behavior.

@jeremystretch commented on GitHub (May 18, 2021): Please update your post above to indicate the _specific values_ for each object being created, so that someone else can try reproducing the reported behavior.
adam commented 2025-12-29 19:22:18 +01:00
Author
Owner
Copy Link

@networkhorse commented on GitHub (May 18, 2021):

Updated @jeremystretch :-)

@networkhorse commented on GitHub (May 18, 2021): Updated @jeremystretch :-)
adam commented 2025-12-29 19:22:18 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 18, 2021):

This is expected behavior. 1.0.0.0/26 is indented two places because it is situated at a depth of two in the hierarchy. The applied filter has no bearing on the hierarchy; if it did, the hierarchy would become quite useless in myriad circumstances.

@jeremystretch commented on GitHub (May 18, 2021): This is expected behavior. 1.0.0.0/26 is indented two places because it is situated at a depth of two in the hierarchy. The applied filter has no bearing on the hierarchy; if it did, the hierarchy would become quite useless in myriad circumstances.
adam commented 2025-12-29 19:22:19 +01:00
Author
Owner
Copy Link

@networkhorse commented on GitHub (May 18, 2021):

@jeremystretch I ask that you reconsider closing this issue because it is highly misleading seeing this

image

There must be a better way of displaying this. Perhaps there is some way of showing the context for the indentation without directly saying "this is related to this site".

@networkhorse commented on GitHub (May 18, 2021): @jeremystretch I ask that you reconsider closing this issue because it is highly misleading seeing this ![image](https://user-images.githubusercontent.com/22162629/118712049-3736db80-b818-11eb-81bb-39002eccd187.png) There must be a better way of displaying this. Perhaps there is some way of showing the context for the indentation without directly saying "this is related to this site".
adam commented 2025-12-29 19:22:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 18, 2021):

You're welcome to open a feature request detailing a specific proposal to improve the display, however this in itself is not a bug. Also note that #6087 may effect significant changes in the way the prefix hierarchy is rendered in the near future.

@jeremystretch commented on GitHub (May 18, 2021): You're welcome to open a feature request detailing a **specific proposal** to improve the display, however this in itself is not a bug. Also note that #6087 may effect significant changes in the way the prefix hierarchy is rendered in the near future.
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
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#4921
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?