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

Make it possible to customize the default value for choice-set fields of various models (DCIM) #9279

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

Originally created by @ihumster on GitHub (Feb 22, 2024).

NetBox version

v3.7.3

Feature type

New functionality

Proposed functionality

Ability to configure default values ​​for fields in forms for creating new items.

Use case

For example, I need to change the default value of the status field for new Devices (Planned instead Active).

Database changes

No response

External dependencies

No response

Originally created by @ihumster on GitHub (Feb 22, 2024). ### NetBox version v3.7.3 ### Feature type New functionality ### Proposed functionality Ability to configure default values ​​for fields in forms for creating new items. ### Use case For example, I need to change the default value of the `status` field for new `Devices` (`Planned` instead `Active`). ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: revisions needed labels 2025-12-29 20:47:47 +01:00
adam closed this issue 2025-12-29 20:47:47 +01:00
adam commented 2025-12-29 20:47:47 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 4, 2024):

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 (Apr 4, 2024): 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 20:47:48 +01:00
Author
Owner
Copy Link

@ihumster commented on GitHub (Apr 4, 2024):

@jeremystretch I'm not a developer and can't offer a description of the required changes to the codebase or database or views/api.

Use case for this functionality is lifecycle of devices in ours (and not only in ours) company - devices starts with
planned status (They may be purchased, located at a supplier or warehouse, or even rack-mounted, but not yet in active status). It would be nice to be able to change the default status for newly created devices (now as I understand it, this is hadrcode).

@ihumster commented on GitHub (Apr 4, 2024): @jeremystretch I'm not a developer and can't offer a description of the required changes to the codebase or database or views/api. Use case for this functionality is lifecycle of devices in ours (and not only in ours) company - devices starts with `planned` status (They may be purchased, located at a supplier or warehouse, or even rack-mounted, but not yet in `active` status). It would be nice to be able to change the default status for newly created devices (now as I understand it, this is hadrcode).
adam commented 2025-12-29 20:47:48 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (May 15, 2024):

I'm going to close this out as no reasonably detailed implementation has been proposed. If anyone would like to spend some time thinking through that and sharing a plan, I'll be happy to re-open the issue for further discussion.

@jeremystretch commented on GitHub (May 15, 2024): I'm going to close this out as no reasonably detailed implementation has been proposed. If anyone would like to spend some time thinking through that and sharing a plan, I'll be happy to re-open the issue for further discussion.
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#9279
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?