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

rack reservations - add role field #10938

New Issue
Closed
opened 2025-12-29 21:37:59 +01:00 by adam · 1 comment
adam commented 2025-12-29 21:37:59 +01:00
Owner
Copy Link

Originally created by @ITJamie on GitHub (Mar 21, 2025).

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

add "role" choice field (it could use the rack roles as a source list or a dedicated roles list)

Use case

being able to document the usecase for a reservation would be useful.

some reservations are very obvious (mostly colocation) but in a lot of cases we have reservations in racks for proposed networking or power usecases.

being able to easily filter down reservations to their usecase would be great

Database changes

add role choice field to reservations model

External dependencies

No response

Originally created by @ITJamie on GitHub (Mar 21, 2025). ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality add "role" choice field (it could use the rack roles as a source list or a dedicated roles list) ### Use case being able to document the usecase for a reservation would be useful. some reservations are very obvious (mostly colocation) but in a lot of cases we have reservations in racks for proposed networking or power usecases. being able to easily filter down reservations to their usecase would be great ### Database changes add role choice field to reservations model ### External dependencies _No response_
adam added the type: feature label 2025-12-29 21:37:59 +01:00
adam closed this issue 2025-12-29 21:37:59 +01:00
adam commented 2025-12-29 21:37:59 +01:00
Author
Owner
Copy Link

@jnovinger commented on GitHub (Mar 27, 2025):

It seems like this is something that could be handled fairly easily with custom fields with a set of custom choices. Rack roles would be a bit to esoteric for a core field--we don't want to over-complicate the data model.

@jnovinger commented on GitHub (Mar 27, 2025): It seems like this is something that could be handled fairly easily with custom fields with a set of custom choices. Rack roles would be a bit to esoteric for a core field--we don't want to over-complicate the data model.
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#10938
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?