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

Site Archive / Decommissioning Feature #1443

New Issue
Closed
opened 2025-12-29 16:32:14 +01:00 by adam · 4 comments
adam commented 2025-12-29 16:32:14 +01:00
Owner
Copy Link

Originally created by @rsaturns on GitHub (Dec 7, 2017).

Issue type

[X] Feature request
[ ] Bug report
[ ] Documentation

Description

Provide the ability to mark a site and all associated attributes as "Archived / Decommissioned / Inactive".

Rational:
There might be a period wherein a location is no longer needed. However, you might want to track information about it for a period of time after it is decommissioned. For example, ensuring circuits are turned down, equipment is returned etc. It would be nice to have a way to denote the site is no longer around / active thereby excluding it from searches and providing visual acuity (Green check / red X / status field etc.) when looking at all listed sites / equipment / subnets / circuits.

Proposal:
At the site level, provide a default status of Active when a site is added. However, there could be a drop down or checkbox when editing the site would allow you to mark it and all child objects associated with it inactive. Until such time you then decide to delete it.

Originally created by @rsaturns on GitHub (Dec 7, 2017). ### Issue type [X] Feature request <!-- An enhancement of existing functionality --> [ ] Bug report <!-- Unexpected or erroneous behavior --> [ ] Documentation <!-- A modification to the documentation --> ### Description Provide the ability to mark a site and all associated attributes as "Archived / Decommissioned / Inactive". **Rational:** There might be a period wherein a location is no longer needed. However, you might want to track information about it for a period of time after it is decommissioned. For example, ensuring circuits are turned down, equipment is returned etc. It would be nice to have a way to denote the site is no longer around / active thereby excluding it from searches and providing visual acuity (Green check / red X / status field etc.) when looking at all listed sites / equipment / subnets / circuits. **Proposal:** At the site level, provide a default status of Active when a site is added. However, there could be a drop down or checkbox when editing the site would allow you to mark it and all child objects associated with it inactive. Until such time you then decide to delete it.
adam added the type: feature label 2025-12-29 16:32:14 +01:00
adam closed this issue 2025-12-29 16:32:14 +01:00
adam commented 2025-12-29 16:32:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Dec 20, 2017):

Provide the ability to mark a site and all associated attributes as "Archived / Decommissioned / Inactive".

If this proposal is merely to add a filterable status field on the Site model (like we have for devices), I think it makes sense. However, it would not be practical to try and explicitly extend that status to all objects related to a site. Just want to clarify the intention here.

@jeremystretch commented on GitHub (Dec 20, 2017): > Provide the ability to mark a site **and all associated attributes** as "Archived / Decommissioned / Inactive". If this proposal is merely to add a filterable `status` field on the Site model (like we have for devices), I think it makes sense. However, it would not be practical to try and explicitly extend that status to all objects related to a site. Just want to clarify the intention here.
adam commented 2025-12-29 16:32:14 +01:00
Author
Owner
Copy Link

@lampwins commented on GitHub (Dec 20, 2017):

I like the idea of just the site status provided that status could be included wherever the site is referenced in the UI. So for example on a device page for site that has a "Decommissioned" status, the bread crumbs would say Region > Site (Decommissioned) > Rack Group > Rack etc. And in the device details for site it would say Site (Decommissioned) and so forth. I think that would be pretty simple to implement via the __str__ method.

@lampwins commented on GitHub (Dec 20, 2017): I like the idea of just the site status provided that status could be included wherever the site is referenced in the UI. So for example on a device page for site that has a "Decommissioned" status, the bread crumbs would say `Region > Site (Decommissioned) > Rack Group > Rack` etc. And in the device details for site it would say `Site (Decommissioned)` and so forth. I think that would be pretty simple to implement via the `__str__` method.
adam commented 2025-12-29 16:32:14 +01:00
Author
Owner
Copy Link

@rsaturns commented on GitHub (Dec 21, 2017):

I would agree with @lampwins in the context of providing some visibility say in the bread crumbs. Also, I think the ability just to filter sites on their status would satisfy the requirement. So far most people tend to navigate from Site > (desired object) not the other way. So if they browse into an inactive site they should quickly know what's going on.

Thanks.

@rsaturns commented on GitHub (Dec 21, 2017): I would agree with @lampwins in the context of providing some visibility say in the bread crumbs. Also, I think the ability just to filter sites on their status would satisfy the requirement. So far most people tend to navigate from Site > (desired object) not the other way. So if they browse into an inactive site they should quickly know what's going on. Thanks.
adam commented 2025-12-29 16:32:14 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jan 25, 2018):

Implemented in ed10a99

@jeremystretch commented on GitHub (Jan 25, 2018): Implemented in ed10a99
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#1443
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?