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 "Maintenance" as a status for devices #9208

New Issue
Closed
opened 2025-12-29 20:47:04 +01:00 by adam · 3 comments
adam commented 2025-12-29 20:47:04 +01:00
Owner
Copy Link

Originally created by @aaron-iles on GitHub (Feb 7, 2024).

NetBox version

v3.6.9

Feature type

Change to existing functionality

Proposed functionality

Acknowledging that this issue has already been raised in #4283 , I am requesting that "Maintenance" be added as a status to devices.

Use case

Introduction

Again acknowledging that this was discussed in #4283 , our team sees "Maintenance" as a status that is fairly long lived at times in our use case (sometimes weeks). We don't necessary care about the previous status when maintenance is complete since we will reevaluate it and update the status as necessary.

Examples

  • A device with a status of "Active" gets into a funky state that requires attention. The device's status is changed to "Maintenance" while techs evaluate it. They discover a new part is needed and two weeks later, the part arrives. After installation, the device is reevaluated to determine its new status.
  • A device with a status of "Active" is working properly, but requires an upgrade of a part. The device's status is changed to "Maintenance" while the upgrade is performed. The upgrade finishes 3 days later and the device is tested to determine its new status. Tests indicate a severe problem prompting us to change the status to "Failed".
  • A device with a status of "Inventory" is currently not in use. Needs dictate that it be turned on and brought into service. Before this can be done, it needs parts replaced to be compatible with the rest of the pool of resources. The status is changed to "Maintenance". When the replacements are complete and tests succeed, the device's status is changed to "Active".

Database changes

No response

External dependencies

No response

Originally created by @aaron-iles on GitHub (Feb 7, 2024). ### NetBox version v3.6.9 ### Feature type Change to existing functionality ### Proposed functionality Acknowledging that this issue has already been raised in #4283 , I am requesting that "Maintenance" be added as a status to devices. ### Use case ### Introduction Again acknowledging that this was discussed in #4283 , our team sees "Maintenance" as a status that is fairly long lived at times in our use case (sometimes weeks). We don't necessary care about the previous status when maintenance is complete since we will reevaluate it and update the status as necessary. ### Examples - A device with a status of "Active" gets into a funky state that requires attention. The device's status is changed to "Maintenance" while techs evaluate it. They discover a new part is needed and two weeks later, the part arrives. After installation, the device is reevaluated to determine its new status. - A device with a status of "Active" is working properly, but requires an upgrade of a part. The device's status is changed to "Maintenance" while the upgrade is performed. The upgrade finishes 3 days later and the device is tested to determine its new status. Tests indicate a severe problem prompting us to change the status to "Failed". - A device with a status of "Inventory" is currently not in use. Needs dictate that it be turned on and brought into service. Before this can be done, it needs parts replaced to be compatible with the rest of the pool of resources. The status is changed to "Maintenance". When the replacements are complete and tests succeed, the device's status is changed to "Active". ### Database changes _No response_ ### External dependencies _No response_
adam added the type: featurestatus: duplicate labels 2025-12-29 20:47:04 +01:00
adam closed this issue 2025-12-29 20:47:04 +01:00
adam commented 2025-12-29 20:47:05 +01:00
Author
Owner
Copy Link

@aaron-iles commented on GitHub (Feb 7, 2024):

I have already completed all of the changes to the code and added unit tests.

@aaron-iles commented on GitHub (Feb 7, 2024): I have already completed all of the changes to the code and added unit tests.
adam commented 2025-12-29 20:47:05 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Feb 7, 2024):

We declined to add this as a stock choice in #4283 for the reason given here. If you want to add this as a choice in your own NetBox deployment, you can do so by defining custom choices for dcim.Device.status.

@jeremystretch commented on GitHub (Feb 7, 2024): We declined to add this as a stock choice in #4283 for the reason given [here](https://github.com/netbox-community/netbox/issues/4283#issuecomment-592555768). If you want to add this as a choice in your own NetBox deployment, you can do so by defining [custom choices](https://docs.netbox.dev/en/stable/configuration/data-validation/#field_choices) for `dcim.Device.status`.
adam commented 2025-12-29 20:47:06 +01:00
Author
Owner
Copy Link

@aaron-iles commented on GitHub (Feb 8, 2024):

I was not aware of the ability to nicely inject extra choices like that. Awesome idea! Thank you for pointing that out.

@aaron-iles commented on GitHub (Feb 8, 2024): I was not aware of the ability to nicely inject extra choices like that. Awesome idea! Thank you for pointing that out.
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 status: duplicate 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#9208
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?