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

virtual machines - status list - new "Paused" or "Suspended" option #10658

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

Originally created by @ITJamie on GitHub (Jan 16, 2025).

Originally assigned to: @antoinekh on GitHub.

NetBox version

v4.2.1

Feature type

Change to existing functionality

Triage priority

N/A

Proposed functionality

add "Paused" or "Suspended" to list of default vm status's

Use case

most Virtualisation solutions allow vm's to be paused or suspended.
The default list of status fields for vm's should be extended to allow for documenting this
(I know the list can be extended by modifying configuration files, but it feels like this should be part of the default list)

Database changes

No response

External dependencies

No response

Originally created by @ITJamie on GitHub (Jan 16, 2025). Originally assigned to: @antoinekh on GitHub. ### NetBox version v4.2.1 ### Feature type Change to existing functionality ### Triage priority N/A ### Proposed functionality add "Paused" or "Suspended" to list of default vm status's ### Use case most Virtualisation solutions allow vm's to be paused or suspended. The default list of status fields for vm's should be extended to allow for documenting this (I know the list can be extended by modifying configuration files, but it feels like this should be part of the default list) ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: featurecomplexity: low labels 2025-12-29 21:34:18 +01:00
adam closed this issue 2025-12-29 21:34:19 +01:00
adam commented 2025-12-29 21:34:19 +01:00
Author
Owner
Copy Link

@antoinekh commented on GitHub (Feb 2, 2025):

I can handle it if needed.
To be honest the hardest part knowing which color is the best for each status

@antoinekh commented on GitHub (Feb 2, 2025): I can handle it if needed. To be honest the hardest part knowing which color is the best for each status
adam commented 2025-12-29 21:34:19 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 3, 2025):

@antoinekh assigned to you.

IMO it's okay to reuse colors (sparingly) for similar statuses.

@jeremystretch commented on GitHub (Feb 3, 2025): @antoinekh assigned to you. IMO it's okay to reuse colors (sparingly) for similar statuses.
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#10658
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?