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

Default values #6464

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

Originally created by @rfl64 on GitHub (May 9, 2022).

NetBox version

v3.2.2

Feature type

Data model extension

Proposed functionality

Could be interesting and time saving setting default values on some items.

Use case

in general, switches, routers, and other network devices use interfaces in access mode and native vlan 1. Only a few interfaces use tagged mode to uplink to other network devices like aps, other switches, etc.

Why not set default estate or value to interfaces?

Database changes

set default values based on statistics or user selection

External dependencies

No response

Originally created by @rfl64 on GitHub (May 9, 2022). ### NetBox version v3.2.2 ### Feature type Data model extension ### Proposed functionality Could be interesting and time saving setting default values on some items. ### Use case in general, switches, routers, and other network devices use interfaces in access mode and native vlan 1. Only a few interfaces use tagged mode to uplink to other network devices like aps, other switches, etc. Why not set default estate or value to interfaces? ### Database changes set default values based on statistics or user selection ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 19:41:00 +01:00
adam closed this issue 2025-12-29 19:41:00 +01:00
adam commented 2025-12-29 19:41:01 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 10, 2022):

Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our contributing guide, a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.

@jeremystretch commented on GitHub (May 10, 2022): Thank you for your interest in extending NetBox. Unfortunately, the information you have provided does not constitute an actionable feature request. Per our [contributing guide](https://github.com/netbox-community/netbox/blob/develop/CONTRIBUTING.md), a feature request must include a thorough description of the proposed functionality, including any database changes, new views or API endpoints, and so on. It must also include a detailed use case justifying its implementation. If you would like to elaborate on your proposal, please modify your post above. If sufficient detail is not added, this issue will be closed.
adam commented 2025-12-29 19:41:01 +01:00
Author
Owner
Copy Link

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

Closing as there's been no further response.

@jeremystretch commented on GitHub (May 18, 2022): Closing as there's been no further response.
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: revisions needed 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#6464
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?