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

Show vlan and range data on IPAM role views #5499

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

Originally created by @marinbernard-pep06 on GitHub (Oct 8, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.6

Feature type

Change to existing functionality

Proposed functionality

NetBox allows to assign IPAM roles to prefixes, ranges and vLANs. I propose to add vlan and range data to the current role views.

On role list (/ipam/roles/)

The page listing the roles includes columns showing the number of prefixes and vLANs referencing each role. I propose to add a third column showing the same info for IP ranges.

On role pages (/ipam/role/<uid>)

On its own page, each role shows the count of all prefixes referencing the role, then lists them in an subtable. I propose to add the same data for vlans and ranges.

Use case

Before support for IP ranges was introduced, we used to represent ranges with container prefixes. We often browse those prefixes by role, using the prefix count links to quickly list all prefixes belonging to a role.

Now that IP ranges are available, we'd like to migrate those container prefixes to proper range objects. But the current views won't allow us to browse ranges as easily as prefixes.

Database changes

None.

External dependencies

None.

Originally created by @marinbernard-pep06 on GitHub (Oct 8, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.6 ### Feature type Change to existing functionality ### Proposed functionality NetBox allows to assign IPAM roles to prefixes, ranges and vLANs. I propose to add vlan and range data to the current role views. ## On role list (`/ipam/roles/`) The page listing the roles includes columns showing the number of prefixes and vLANs referencing each role. I propose to add a third column showing the same info for IP ranges. ## On role pages (`/ipam/role/<uid>`) On its own page, each role shows the count of all prefixes referencing the role, then lists them in an subtable. I propose to add the same data for vlans and ranges. ### Use case Before support for IP ranges was introduced, we used to represent ranges with container prefixes. We often browse those prefixes by role, using the prefix count links to quickly list all prefixes belonging to a role. Now that IP ranges are available, we'd like to migrate those container prefixes to proper range objects. But the current views won't allow us to browse ranges as easily as prefixes. ### Database changes None. ### External dependencies None.
adam added the status: acceptedtype: feature labels 2025-12-29 19:28:44 +01:00
adam closed this issue 2025-12-29 19:28:44 +01:00
adam commented 2025-12-29 19:28:44 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 11, 2022):

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.

@github-actions[bot] commented on GitHub (Jan 11, 2022): 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).
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#5499
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?