starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-13 13:53:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Allow default statuses to be customised #1173

New Issue
Closed
opened 2025-12-29 16:29:42 +01:00 by adam · 8 comments
adam commented 2025-12-29 16:29:42 +01:00
Owner
Copy Link

Originally created by @cmccallan on GitHub (Aug 14, 2017).

Issue type: Feature Request

Python version:
NetBox version:

Currently when new IP addresses, Prefixes and VLANs are created their Status is defaulted to Active. This sometimes leads to issues of Netbox no longer being a source of truth if someone creates an IP/prefix/vlan and doesn't know/realise that it needs to be set to Reserved until it is actually active.
What we'd ideally like to have is to be able to set Reserved to be the default, and then it can be changed to Active/Deprecated/DHCP when it is actually in that state. This would prevent having multiple IPs/prefixes/VLANs assigned Active that are not and improve reliability of our setup.

Originally created by @cmccallan on GitHub (Aug 14, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> Issue type: Feature Request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> Currently when new IP addresses, Prefixes and VLANs are created their Status is defaulted to Active. This sometimes leads to issues of Netbox no longer being a source of truth if someone creates an IP/prefix/vlan and doesn't know/realise that it needs to be set to Reserved until it is actually active. What we'd ideally like to have is to be able to set Reserved to be the default, and then it can be changed to Active/Deprecated/DHCP when it is actually in that state. This would prevent having multiple IPs/prefixes/VLANs assigned Active that are not and improve reliability of our setup.
adam added the type: featurestatus: needs ownerpending closure labels 2025-12-29 16:29:42 +01:00
adam closed this issue 2025-12-29 16:29:42 +01:00
adam commented 2025-12-29 16:29:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 15, 2017):

This is similar to #492 (and probably some others) in that it would require a mechanism for storing preferences for individual users. I'd like to implement a simple sort of key/value store for this (rather than continually extending a profile model). Need to look more into what would work best.

@jeremystretch commented on GitHub (Aug 15, 2017): This is similar to #492 (and probably some others) in that it would require a mechanism for storing preferences for individual users. I'd like to implement a simple sort of key/value store for this (rather than continually extending a profile model). Need to look more into what would work best.
adam commented 2025-12-29 16:29:43 +01:00
Author
Owner
Copy Link

@cmccallan commented on GitHub (Aug 15, 2017):

Potential workaround could be making it a mandatory field and setting default to a null value? Might not be ideal but would prevent wrong provisioning if a user has to manually select a status.

@cmccallan commented on GitHub (Aug 15, 2017): Potential workaround could be making it a mandatory field and setting default to a null value? Might not be ideal but would prevent wrong provisioning if a user has to manually select a status.
adam commented 2025-12-29 16:29:43 +01:00
Author
Owner
Copy Link

@puck commented on GitHub (Aug 21, 2017):

For simple arbitrary key/value store, see the JSONB data type I just mentioned on #1349. :)

@puck commented on GitHub (Aug 21, 2017): For simple arbitrary key/value store, see the JSONB data type I just mentioned on #1349. :)
adam commented 2025-12-29 16:29:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Oct 9, 2017):

@puck v2.2 will require PostgreSQL 9.4+ to support JSONB anyway (for storing report data), so that's a very appealing solution.

@jeremystretch commented on GitHub (Oct 9, 2017): @puck v2.2 will require PostgreSQL 9.4+ to support JSONB anyway (for storing report data), so that's a very appealing solution.
adam commented 2025-12-29 16:29:43 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jun 24, 2019):

Blocked by #3294

@jeremystretch commented on GitHub (Jun 24, 2019): Blocked by #3294
adam commented 2025-12-29 16:29:44 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 24, 2020):

Rather than requiring the user to pick a specific default status (for this and numerous other objects), it might make more sense for NetBox to "remember" the last-chosen status used when creating/editing that type of object. This would work similarly to how NetBox remembers table column preferences for individual users.

@jeremystretch commented on GitHub (Jul 24, 2020): Rather than requiring the user to pick a specific default status (for this and numerous other objects), it might make more sense for NetBox to "remember" the last-chosen status used when creating/editing that type of object. This would work similarly to how NetBox remembers table column preferences for individual users.
adam commented 2025-12-29 16:29:44 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Oct 16, 2020):

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.

@stale[bot] commented on GitHub (Oct 16, 2020): 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 16:29:44 +01:00
Author
Owner
Copy Link

@stale[bot] commented on GitHub (Oct 31, 2020):

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.

@stale[bot] commented on GitHub (Oct 31, 2020): 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 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#1173
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?