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 VLAN scope to VLAN form fields (API-Select) #7153

New Issue
Closed
opened 2025-12-29 20:19:52 +01:00 by adam · 4 comments
adam commented 2025-12-29 20:19:52 +01:00
Owner
Copy Link

Originally created by @DanSheps on GitHub (Oct 24, 2022).

NetBox version

v.3.3.5

Feature type

Change to existing functionality

Proposed functionality

Add "(Site: )" or "(Scope Type: Scope)" to name display for API requests

This can be done by overriding "get_display" property on the serializer, which appears to have been done for a few models already.

Use case

Currently, in a filter form field or form field for a vlan, if you have multiple VLANs with the same name but different scopes (Global, Site, VLAN Group(s)) there is no easy way to differentiate them.

Simply using this would allow easier differentiation between all objects.

Database changes

None

External dependencies

None

Originally created by @DanSheps on GitHub (Oct 24, 2022). ### NetBox version v.3.3.5 ### Feature type Change to existing functionality ### Proposed functionality Add "(Site: <site>)" or "(Scope Type: Scope)" to name display for API requests This can be done by overriding "get_display" property on the serializer, which appears to have been done for a few models already. ### Use case Currently, in a filter form field or form field for a vlan, if you have multiple VLANs with the same name but different scopes (Global, Site, VLAN Group(s)) there is no easy way to differentiate them. Simply using this would allow easier differentiation between all objects. ### Database changes None ### External dependencies None
adam added the type: feature label 2025-12-29 20:19:52 +01:00
adam closed this issue 2025-12-29 20:19:53 +01:00
adam commented 2025-12-29 20:19:53 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Dec 24, 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. 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 (Dec 24, 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. **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 20:19:54 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Dec 30, 2022):

I am going to tentatively work on this in early January, but if someone wants to propose something it is free to pickup. This should be a pretty easy PR for anyone looking to get started on something.

@DanSheps commented on GitHub (Dec 30, 2022): I am going to tentatively work on this in early January, but if someone wants to propose something it is free to pickup. This should be a pretty easy PR for anyone looking to get started on something.
adam commented 2025-12-29 20:19:54 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Mar 31, 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 (Mar 31, 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 20:19:54 +01:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Apr 30, 2023):

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.

@github-actions[bot] commented on GitHub (Apr 30, 2023): 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 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#7153
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?