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

Assign existing prefix to VLAN, starting from VLAN view #5152

New Issue
Closed
opened 2025-12-29 19:24:51 +01:00 by adam · 6 comments
adam commented 2025-12-29 19:24:51 +01:00
Owner
Copy Link

Originally created by @sdktr on GitHub (Aug 6, 2021).

NetBox version

v2.11.10

Feature type

Change to existing functionality

Proposed functionality

When attaching a prefix to a VLAN there are two routes in the GUI:

  1. Open the prefix and choose a VLAN using the vlan filters OR
  2. Open the VLAN and click 'add prefix'

Scenario 2 closely repeats the workflow for assigning an IP to an interface. In that selector there is an option to assign an already known IP instead of creating a new instance.
Assigning a prefix to a vlan would benefit from an 'assign' option as well.

Use case

When starting from a VLAN, trying to attach an existing prefix requires opening a new set of tabs to look up the prefix and starting the association from there. Attaching an already known prefix would save quite some clicks.

Database changes

N/A

External dependencies

N/A

Originally created by @sdktr on GitHub (Aug 6, 2021). ### NetBox version v2.11.10 ### Feature type Change to existing functionality ### Proposed functionality When attaching a prefix to a VLAN there are two routes in the GUI: 1) Open the prefix and choose a VLAN using the vlan filters OR 2) Open the VLAN and click 'add prefix' Scenario 2 closely repeats the workflow for assigning an IP to an interface. In that selector there is an option to assign an already known IP instead of creating a new instance. Assigning a prefix to a vlan would benefit from an 'assign' option as well. ### Use case When starting from a VLAN, trying to attach an existing prefix requires opening a new set of tabs to look up the prefix and starting the association from there. Attaching an already known prefix would save quite some clicks. ### Database changes N/A ### External dependencies N/A
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 19:24:51 +01:00
adam closed this issue 2025-12-29 19:24:51 +01:00
adam commented 2025-12-29 19:24:51 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Nov 9, 2021):

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 (Nov 9, 2021): 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 19:24:52 +01:00
Author
Owner
Copy Link

@rhyser9 commented on GitHub (Nov 16, 2021):

I can try implementing this.

Using the existing IP Address Add / Assign setup as an example, it looks like this will involve adding a prefixes/assign URL, PrefixAssignView, PrefixAssignForm, PrefixAssignTable, inc/prefix_edit_header.html, prefix_edit.html, and prefix_assign.html.

@rhyser9 commented on GitHub (Nov 16, 2021): I can try implementing this. Using the existing IP Address Add / Assign setup as an example, it looks like this will involve adding a `prefixes/assign` URL, `PrefixAssignView`, `PrefixAssignForm`, `PrefixAssignTable`, `inc/prefix_edit_header.html`, `prefix_edit.html`, and `prefix_assign.html`.
adam commented 2025-12-29 19:24:52 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 17, 2021):

Assigned to you @rhyser9

@DanSheps commented on GitHub (Nov 17, 2021): Assigned to you @rhyser9
adam commented 2025-12-29 19:24:52 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 6, 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 6, 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).
adam commented 2025-12-29 19:24:53 +01:00
Author
Owner
Copy Link

@AnythingOverIP commented on GitHub (Apr 20, 2023):

Is this something that is or will be addressed in 3.5? It would follow the logic behind other processes (i.e assigning an existing IP to an interface instead of creating a new one).

@AnythingOverIP commented on GitHub (Apr 20, 2023): Is this something that is or will be addressed in 3.5? It would follow the logic behind other processes (i.e assigning an existing IP to an interface instead of creating a new one).
adam commented 2025-12-29 19:24:53 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 30, 2023):

It doesn't appear that any feasible solution has been offered, so I'm going to close this out. We might revisit this in the future once the UI has been revamped per #12128.

@jeremystretch commented on GitHub (May 30, 2023): It doesn't appear that any feasible solution has been offered, so I'm going to close this out. We might revisit this in the future once the UI has been revamped per #12128.
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#5152
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?