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 Information #1160

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

Originally created by @kopacko on GitHub (Aug 9, 2017).

Issue type: Feature Request

Python version:
NetBox version:

This feature request is related to site and tenant information. In tracking our sites and providing data related to a site, it would be nice to have the ability to add custom sections or critical contact information related to power, HVAC, building management, etc. Most of this information is incredibly important from an outage/disaster perspective and would information that would apply to an entire building (not necessarily tenant specific, but maybe).

It would be nice to have the same ability within the tenant information for pertinent internal contact information, vendor support information, etc related to a location.

Originally created by @kopacko on GitHub (Aug 9, 2017). <!-- Please note: GitHub issues are to be used only for feature requests and bug reports. For installation assistance or general discussion, please join us on the mailing list: https://groups.google.com/forum/#!forum/netbox-discuss Please indicate "bug report" or "feature request" below. Be sure to search the existing set of issues (both open and closed) to see if a similar issue has already been raised. --> ### Issue type: Feature Request <!-- If filing a bug, please indicate the version of Python and NetBox you are running. (This is not necessary for feature requests.) --> **Python version:** **NetBox version:** <!-- If filing a bug, please record the exact steps taken to reproduce the bug and any errors messages that are generated. If filing a feature request, please precisely describe the data model or workflow you would like to see implemented, and provide a use case. --> This feature request is related to site and tenant information. In tracking our sites and providing data related to a site, it would be nice to have the ability to add custom sections or critical contact information related to power, HVAC, building management, etc. Most of this information is incredibly important from an outage/disaster perspective and would information that would apply to an entire building (not necessarily tenant specific, but maybe). It would be nice to have the same ability within the tenant information for pertinent internal contact information, vendor support information, etc related to a location.
adam closed this issue 2025-12-29 16:29:36 +01:00
adam commented 2025-12-29 16:29:37 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Aug 9, 2017):

You may want to add custom fields for some of this, but please keep in mind that NetBox is primarily an IPAM/DCIM application and does not address facilities management. #1344 has been opened to explore the possibility of more flexible contact assignment.

@jeremystretch commented on GitHub (Aug 9, 2017): You may want to add custom fields for some of this, but please keep in mind that NetBox is primarily an IPAM/DCIM application and does not address facilities management. #1344 has been opened to explore the possibility of more flexible contact assignment.
adam commented 2025-12-29 16:29:37 +01:00
Author
Owner
Copy Link

@kopacko commented on GitHub (Aug 9, 2017):

Well add me to the list for the DC contact/support info request. That's pretty important for a site.

@kopacko commented on GitHub (Aug 9, 2017): Well add me to the list for the DC contact/support info request. That's pretty important for a site.
adam commented 2025-12-29 16:29:38 +01:00
Author
Owner
Copy Link

@slindermann commented on GitHub (Jan 19, 2018):

Please add me to the list as well. More / Custom site information fields (optional!) would be very helpful in our scenario.

@slindermann commented on GitHub (Jan 19, 2018): Please add me to the list as well. More / Custom site information fields (optional!) would be very helpful in our scenario.
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
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#1160
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?