starred/netbox
1
0
Fork 0
mirror of https://github.com/netbox-community/netbox.git synced 2026-01-12 05:20:31 +01:00
Code Issues 273 Packages Projects Releases 10 Wiki Activity

Location Status #5608

New Issue
Closed
opened 2025-12-29 19:30:07 +01:00 by adam · 4 comments
adam commented 2025-12-29 19:30:07 +01:00
Owner
Copy Link

Originally created by @ryanmerolle on GitHub (Nov 4, 2021).

Originally assigned to: @jeremystretch on GitHub.

NetBox version

v3.0.9

Feature type

Data model extension

Proposed functionality

Add status to location object. Add the same statuses as site model.

Use case

Add status to Location. For users tracking office suites, colocation cages, etc in a larger site that may have multiple locations under it, it would be ideal to allow for status to be associated to a location.

Database changes

No response

External dependencies

No response

Originally created by @ryanmerolle on GitHub (Nov 4, 2021). Originally assigned to: @jeremystretch on GitHub. ### NetBox version v3.0.9 ### Feature type Data model extension ### Proposed functionality Add status to location object. Add the same statuses as site model. ### Use case Add status to Location. For users tracking office suites, colocation cages, etc in a larger site that may have multiple locations under it, it would be ideal to allow for status to be associated to a location. ### Database changes _No response_ ### External dependencies _No response_
adam added the status: acceptedtype: feature labels 2025-12-29 19:30:07 +01:00
adam closed this issue 2025-12-29 19:30:07 +01:00
adam commented 2025-12-29 19:30:08 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 4, 2021):

Add status to Location. For users tracking office suites, colocation cages, etc in a larger site that may have multiple locations under it, it would be ideal to allow for status to be associated to a location.

What kind of statuses? The same as site? (Active, Planned, Staging, Decommissioning, Retired?)

@DanSheps commented on GitHub (Nov 4, 2021): > Add status to Location. For users tracking office suites, colocation cages, etc in a larger site that may have multiple locations under it, it would be ideal to allow for status to be associated to a location. What kind of statuses? The same as site? (Active, Planned, Staging, Decommissioning, Retired?)
adam commented 2025-12-29 19:30:08 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Nov 4, 2021):

Good catch. Updated the issue.

@ryanmerolle commented on GitHub (Nov 4, 2021): Good catch. Updated the issue.
adam commented 2025-12-29 19:30:08 +01:00
Author
Owner
Copy Link

@DanSheps commented on GitHub (Nov 4, 2021):

Yeah, what you were posting made me think more about roles (Office, Datacenter, Comm Closet, Hallway, etc) then statuses. Maybe that could be an additional FR at some point

@DanSheps commented on GitHub (Nov 4, 2021): Yeah, what you were posting made me think more about roles (Office, Datacenter, Comm Closet, Hallway, etc) then statuses. Maybe that could be an additional FR at some point
adam commented 2025-12-29 19:30:08 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Nov 4, 2021):

Location roles would be interesting. Could just call it a location group similar to sites.

@ryanmerolle commented on GitHub (Nov 4, 2021): Location roles would be interesting. Could just call it a location group similar to sites.
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: 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#5608
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?