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

Mapping technicians to a site #4564

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

Originally created by @beermann on GitHub (Feb 12, 2021).

Environment

Python version: 3.6.8
NetBox version: 2.10.4

Proposed Functionality

Associate a technician/staff to a site in order to indicate who has physical access to a site.

Purpose

In order for quick response when an incident happens and on-call needs to figure out who is able to go to a site.
Auditing to show the audit who has access to what.

Originally created by @beermann on GitHub (Feb 12, 2021). Environment Python version: 3.6.8 NetBox version: 2.10.4 Proposed Functionality Associate a technician/staff to a site in order to indicate who has physical access to a site. Purpose In order for quick response when an incident happens and on-call needs to figure out who is able to go to a site. Auditing to show the audit who has access to what.
adam closed this issue 2025-12-29 18:37:43 +01:00
adam commented 2025-12-29 18:37:43 +01:00
Author
Owner
Copy Link

@ryanmerolle commented on GitHub (Feb 12, 2021):

This is not a high ROI feature. It can be solved by pairing with a tool like snipe-it, using a custom field for the site, or using the comments section for a site.

@ryanmerolle commented on GitHub (Feb 12, 2021): This is not a high ROI feature. It can be solved by pairing with a tool like snipe-it, using a custom field for the site, or using the comments section for a site.
adam commented 2025-12-29 18:37:43 +01:00
Author
Owner
Copy Link

@ziggekatten commented on GitHub (Feb 12, 2021):

Or Config Contexts, which imho is a swiss army knife.

@ziggekatten commented on GitHub (Feb 12, 2021): Or Config Contexts, which imho is a swiss army knife.
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#4564
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?