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 additional Status for Racks or Devices #4716

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

Originally created by @markuszeiter on GitHub (Apr 1, 2021).

NetBox version

v2.8.9

Feature type

New functionality

Proposed functionality

I would like to be able to add (on demand in UI or config file) additional RACK or DEVICE STATUS CHOICES.

Use case

For the rack use case we have different states from our data center team which we would like to represent in netbox.

Database changes

not sure

External dependencies

not sure

Originally created by @markuszeiter on GitHub (Apr 1, 2021). ### NetBox version v2.8.9 ### Feature type New functionality ### Proposed functionality I would like to be able to add (on demand in UI or config file) additional RACK or DEVICE STATUS CHOICES. ### Use case For the rack use case we have different states from our data center team which we would like to represent in netbox. ### Database changes not sure ### External dependencies not sure
adam added the type: feature label 2025-12-29 19:19:48 +01:00
adam closed this issue 2025-12-29 19:19:48 +01:00
adam commented 2025-12-29 19:19:49 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Apr 1, 2021):

This has been proposed in the past and we've opted to stick with the hard-coded statuses because they're standardized and more efficient. You also have the option of employing custom fields and/or tags to further classify devices and racks per your needs.

@jeremystretch commented on GitHub (Apr 1, 2021): This has been proposed in the past and we've opted to stick with the hard-coded statuses because they're standardized and more efficient. You also have the option of employing custom fields and/or tags to further classify devices and racks per your needs.
adam commented 2025-12-29 19:19:49 +01:00
Author
Owner
Copy Link

@markuszeiter commented on GitHub (Apr 7, 2021):

@jeremystretch ok, thank you very much for the quick feedback.

@markuszeiter commented on GitHub (Apr 7, 2021): @jeremystretch ok, thank you very much for the quick feedback.
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#4716
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?