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

Possibility to add computers as devices #6701

New Issue
Closed
opened 2025-12-29 19:44:10 +01:00 by adam · 1 comment
adam commented 2025-12-29 19:44:10 +01:00
Owner
Copy Link

Originally created by @pboatone on GitHub (Jul 21, 2022).

NetBox version

v3.2.7

Feature type

New functionality

Proposed functionality

If there is a customer, that want to document their infrastructure and wants to where their computers are located.

-> hostnamename
-> location -> as rooms not as rack
-> user on this computer
-> IP-Adress static or dhcp
-> working system such as Windows 10

Use case

You can find computers fast and know which person is working with it

Database changes

No response

External dependencies

No response

Originally created by @pboatone on GitHub (Jul 21, 2022). ### NetBox version v3.2.7 ### Feature type New functionality ### Proposed functionality If there is a customer, that want to document their infrastructure and wants to where their computers are located. -> hostnamename -> location -> as rooms not as rack -> user on this computer -> IP-Adress static or dhcp -> working system such as Windows 10 ### Use case You can find computers fast and know which person is working with it ### Database changes _No response_ ### External dependencies _No response_
adam added the type: feature label 2025-12-29 19:44:10 +01:00
adam closed this issue 2025-12-29 19:44:10 +01:00
adam commented 2025-12-29 19:44:11 +01:00
Author
Owner
Copy Link

@jeremystretch commented on GitHub (Jul 21, 2022):

NetBox is not designed to track end clients, however there's nothing preventing you from modeling these today should you choose to do so. Please consider starting a discussion if you'd like assistance.

@jeremystretch commented on GitHub (Jul 21, 2022): NetBox is not designed to track end clients, however there's nothing preventing you from modeling these today should you choose to do so. Please consider starting a [discussion](https://github.com/netbox-community/netbox/discussions/new) if you'd like assistance.
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#6701
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?