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

Rack reservations - add status field #10934

New Issue
Closed
opened 2025-12-29 21:37:56 +01:00 by adam · 0 comments
adam commented 2025-12-29 21:37:56 +01:00
Owner
Copy Link

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

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v4.2.5

Feature type

Data model extension

Proposed functionality

add status field choice to rack reservations. (allow customisation of this choices list like many other status fields have)

internally in our org we would have uses for the following statuses:

  • active
  • pending
  • staged
  • proposed
  • hold
  • cancelled

Use case

it would be great if reservations had native status fields.

being able to track active vs proposed vs cancelled colocation reservations would be very useful

Database changes

add status field to rack reservations model

External dependencies

No response

Originally created by @ITJamie on GitHub (Mar 21, 2025). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v4.2.5 ### Feature type Data model extension ### Proposed functionality add status field choice to rack reservations. (allow customisation of this choices list like many other status fields have) internally in our org we would have uses for the following statuses: - active - pending - staged - proposed - hold - cancelled ### Use case it would be great if reservations had native status fields. being able to track active vs proposed vs cancelled colocation reservations would be very useful ### Database changes add status field to rack reservations model ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:37:56 +01:00
adam closed this issue 2025-12-29 21:37:57 +01:00
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 complexity: low status: accepted 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#10934
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?